Issue
Contribution records
Contributors

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

Give credit to everyone
Q2U
jonathanshaw
ecrown volunteering
valthebald volunteering
xjm organization(s): Acquia
ccjjmartin volunteering
paintingguy
Crell organization(s): Upsun (formerly Platform.sh)
yogeshmpawar volunteering organization(s): QED42
alex_optim organization(s): GOLEMS GABB customer(s): GOLEMS GABB
tulvit volunteering
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
kawo organization(s): The University of Edinburgh
jrperry
jds1
catch organization(s): Third and Grove
leolandotan volunteering organization(s): Promet Source
larowlan organization(s): PreviousNext
sean.walker@nreca.coop volunteering
akhil.desai
star-szr volunteering
darren oh volunteering
karthik.baikati 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.