Issue
Contribution records
Contributors

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

Give credit to everyone
volkswagenchick organization(s): Florida DrupalCamp, Red Hat
baddysonja organization(s): 1xINTERNET
dan2k3k4 organization(s): amazee.io
jmolivas organization(s): Octahedroid
mandclu volunteering organization(s): Acquia
mherchel organization(s): Dripyard
weekbeforenext organization(s): Red Hat
mupsi
navneet0693
stewest organization(s): Amazee Labs
ultimike organization(s): DrupalEasy
florismoriceau organization(s): Drupal France & Francophonie
jjcs227 volunteering
laryn organization(s): Aten Design Group, Backdrop CMS
mayankguptadotcom
g.paluch volunteering
gábor hojtsy organization(s): Acquia
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
didier misson volunteering
samitk organization(s): Material customer(s): Drupal India 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.