Issue
Contribution records
Contributors

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

Give credit to everyone
xjm organization(s): Acquia
mlhess volunteering
phenaproxima organization(s): Acquia
anavarre organization(s): Acquia
berdir organization(s): MD Systems GmbH
anybody volunteering organization(s): DROWL.de
marcoscano volunteering
seanb
webchick organization(s): Acquia
bkosborne organization(s): Princeton University
fabianx organization(s): Tag1 Consulting, Inc.
brooke_heaton
traviscarden organization(s): Acquia
alison volunteering
devkinetic organization(s): CommonPlaces Interactive
krystalcode organization(s): Acro Commerce
teknocat
m_hobby organization(s): Circle Interactive
solide-echt
geek-merlin organization(s): Geeks4Change, MachbarMacher
strykaizer volunteering
godotislate volunteering
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.