Issue
Contribution records
Contributors

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

Give credit to everyone
mgifford organization(s): OpenConcept Consulting Inc.
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
dmsmidt volunteering organization(s): Triquanta
tr
xjm organization(s): Acquia
bojanz organization(s): Centarro
rootwork
lokapujya
skaught volunteering
andrewmacpherson volunteering organization(s): Annertech
emarchak organization(s): Myplanet
marcvangend organization(s): Triquanta
kattekrab volunteering organization(s): Catalyst IT, Creative Contingencies
gnuget volunteering organization(s): Agaric
webchick organization(s): Acquia
dries
tim.plunkett organization(s): Acquia
abinayaa.k volunteering
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
roya-rateshtari volunteering
hass
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.