Contribution records
Contributors

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

Give credit to everyone
lauriii lauriii organization(s): Acquia
xjm xjm organization(s): Acquia
mherchel mherchel organization(s): Lullabot
ipwa ipwa organization(s): manifesto
alexpott alexpott organization(s): Acro Commerce, Thunder
rootwork rootwork
rachel_norfolk rachel_norfolk organization(s): Drupal Association
marcel66 marcel66
ressa ressa organization(s): Ardea
brianperry backlineint organization(s): Bounteous
dorianwinterfeld dorianwinterfeld volunteering
davidhernandez davidhernandez organization(s): JAKALA (formerly FFW)
joelpittet joelpittet volunteering organization(s): The University of British Columbia
ahmedsayeed1982 ahmedsayeed1982
jamesoakley JamesOakley volunteering
chi Chi
omd omd
gábor hojtsy goba organization(s): Acquia
rex.barkdoll rex.barkdoll
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.