Issue
Contribution records
Contributors

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

Give credit to everyone
Iriina
philipnorton42 volunteering
aburrows organization(s): DigiDrop
alexpott organization(s): Acro Commerce, Thunder
gambry organization(s): manifesto
justafish volunteering organization(s): Lullabot
rachel_norfolk organization(s): Drupal Association
andrewmacpherson volunteering organization(s): Annertech
corinnewelsh
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
tresti88 organization(s): One
gmidwood
richmoore
blacklabel_tom organization(s): Reason Digital
johnhannawin
jollysolutions
eli-t
john cook organization(s): Creode
Phil Wolstenholme organization(s): CTI Digital
Not Real
jaro.2801
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.