Issue
Contribution records
Contributors

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

Give credit to everyone
pillarsdotnet
boombatower
webchick organization(s): Acquia
forestmonster
jthorson
crashtest_
catch organization(s): Tag1 Consulting, Inc., Third and Grove customer(s): Drupal Association
attiks
xjm volunteering
NROTC_Webmaster
markhalliwell organization(s): Tag1 Consulting, Inc.
thedavidmeister
yesct
drumm organization(s): Drupal Association
dawehner volunteering
klausi
dasjo volunteering
anavarre organization(s): Acquia
stevector organization(s): Pantheon
elachlan
mallezie
jweowu
mile23
Mixologic organization(s): Drupal Association
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
gisle organization(s): Hannemyr Nye Medier AS
markdorison organization(s): Chromatic
kentr volunteering
dave reid
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.