Issue
Contribution records
Contributors

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

Give credit to everyone
cweagans volunteering
neclimdul organization(s): APQC
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
Crell volunteering
fabianx organization(s): Tag1 Consulting, Inc.
catch volunteering organization(s): Third and Grove
aaronbauman organization(s): Message Agency
joachim volunteering
xano
mallezie
andypost volunteering organization(s): Skilld
jhodgdon
hardik_patel_12 organization(s): Portage CyberTech, QED42
jofitz organization(s): jofitz
dpi volunteering organization(s): PreviousNext
alexpott organization(s): Acro Commerce, Thunder
daffie
donquixote volunteering
geek-merlin organization(s): MachbarMacher
tim.plunkett organization(s): Acquia
ambient.impact volunteering
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.