Issue
Contribution records
Contributors

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

Give credit to everyone
adamzimmermann organization(s): Chromatic
natew volunteering
aaronbauman organization(s): Message Agency
klausi organization(s): jobiqo - job board technology
jungle volunteering
mmjvb volunteering
rolodmonkey organization(s): Third and Grove
arlina organization(s): Chapter Three (acquired by Kanopi Studios) customer(s): Apigee
damienmckenna organization(s): Current
jedgar1mx
arkener volunteering
minoroffense organization(s): Coldfront Labs Inc.
mpotter organization(s): Phase2
drumm organization(s): Drupal Association
acbramley organization(s): PreviousNext customer(s): Service NSW
greg.1.anderson organization(s): Pantheon
kim.pepper organization(s): PreviousNext
ion.macaria
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.