Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
jjchinquist jjchinquist organization(s): drunomics, Drupal Austria
dunx dunx organization(s): Zoocha
pdjohnson pdjohnson organization(s): 1xINTERNET
rgladden rgladden organization(s): ImageX
amberhenry amber.henry organization(s): Morpht
wouters_f wouters_frederik organization(s): Dropsolid
slawrence10 slawrence10 volunteering organization(s): Scott Lawrence London
mfernanda.silva mfernanda.silva organization(s): SeeD EM
matthews jmsaunders volunteering organization(s): amazee.io, James Matthew Saunders LLC
james tillotson james_tillotson organization(s): 1xINTERNET
dan2k3k4 dan2k3k4 organization(s): amazee.io
scott falconer scottfalconer organization(s): Acquia
kristen pol kepol organization(s): Itty Bitty Byte, Salsa Digital
zoocha will ZoochaWill organization(s): Zoocha
palakosl palakosl
ben-peter Ben-Peter
johnpicozzi johnpicozzi organization(s): EPAM
lenny moskalyk lenny_moskalyk organization(s): Drupal Association
mandclu mandclu volunteering organization(s): Acquia
pritishkumar pritish.kumar volunteering organization(s): OpenSense Labs
hestenet hestenet organization(s): Drupal Association
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.