Contribution records
Contributors

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

Give credit to everyone
ivanmartil ivanmartil
mherchel mherchel volunteering organization(s): Agileana, Dripyard
dieterholvoet DieterHolvoet organization(s): Minsky
e0ipso e0ipso volunteering organization(s): Lullabot
_utsavsharma utsavsharma6
lauriii lauriii organization(s): Acquia
eelkeblok eelkeblok
catch catch organization(s): Third and Grove
joelsteidl joelsteidl organization(s): Aten Design Group
sethhill sethhill organization(s): Aten Design Group
mglaman mglaman organization(s): Acquia
m4olivei m4olivei organization(s): Lullabot
smustgrave smustgrave organization(s): Mobomo
godotislate godotislate volunteering
gareth.poole gareth.poole organization(s): Sparks Interactive
web-beest Web-Beest organization(s): Web-Beest
petr illek PetrIllek volunteering organization(s): Annertech, CSGov
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.