Issue
Contribution records
Contributors

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

Give credit to everyone
markconroy organization(s): Annertech
lauriii organization(s): Acquia
longwave organization(s): Full Fat Things
alexpott organization(s): Acro Commerce, Thunder
codexmas volunteering organization(s): Acquia
harsha012 volunteering
joelpittet organization(s): The University of British Columbia
leahtard organization(s): The Jibe
mukeysh volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
occupant organization(s): The University of British Columbia
rpayanm organization(s): Agileana
bnjmnm organization(s): Acquia
andy-blum organization(s): Lullabot
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.