Issue
Contribution records
Contributors

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

Give credit to everyone
volkswagenchick organization(s): Kanopi Studios
amykhailova organization(s): Kalamuna
brianperry organization(s): Bounteous
dstol volunteering
kunalkursija organization(s): Axelerant
mikemiles86
shaal volunteering organization(s): Palantir.net
sjshaal volunteering
aaronchristian organization(s): ImageX
MahyaGolabi
gloriaswebtech volunteering
monicadear organization(s): Lullabot
stephenpashby
acouch organization(s): Promet Source
chrisodva
dinarcon organization(s): UnderstandDrupal.com
imalabya organization(s): Specbee customer(s): Drupal India Association
mandclu organization(s): Northern Commerce
shrop organization(s): Current
sparklingrobots organization(s): Pantheon
tedbow organization(s): Acquia
hot_sauce volunteering
jcloys organization(s): Princeton University
mherchel organization(s): Lullabot
pixelite organization(s): Evolving Web
weekbeforenext organization(s): Lullabot
chris mcgrath
mahmoud-zayed organization(s): ImageX
Git commit message
Commit types
  • 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

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.