Issue
Contribution records
Contributors

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

Give credit to everyone
mikeburrelljr volunteering
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
cilefen
naveenvalecha organization(s): Acquia customer(s): Acquia
dixon_
webchick organization(s): Acquia
xjm organization(s): Acquia
jhedstrom organization(s): Phase2
Bojhan volunteering
skwashd organization(s): Dave Hall Consulting
giorgio79
googletorp
jstoller volunteering organization(s): California Science Center
amateescu customer(s): Pfizer, Inc.
platinum1
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
Crell organization(s): Palantir.net customer(s): Acquia
markdorison organization(s): Chromatic
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
catch organization(s): Third and Grove
quietone organization(s): PreviousNext
manjit.singh organization(s): Material
moshe weitzman 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.