Issue
Contribution records
Contributors

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

Give credit to everyone
slasher13 volunteering organization(s): Wolters Kluwer
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
jonathanshaw
martin107 volunteering
rosk0 organization(s): Catalyst IT
mpdonadio organization(s): DiD Agency
jofitz organization(s): ComputerMinds
mile23 volunteering
alexpott organization(s): Acro Commerce
catch organization(s): Third and Grove
deviantintegral organization(s): Lullabot
jibran volunteering
cilefen
pounard
larowlan volunteering organization(s): PreviousNext
andypost volunteering organization(s): Skilld
xjm organization(s): Acquia
webchick organization(s): Acquia
mondrake volunteering
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
moshe weitzman
pritishkumar
tim.plunkett organization(s): Acquia
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.