Issue
Contribution records
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
mpdonadio organization(s): DiD Agency
chx organization(s): Smartsheet
Crell volunteering organization(s): Palantir.net
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
dawehner volunteering
gambry organization(s): manifesto
andypost volunteering organization(s): Skilld
vprocessor organization(s): Skilld
xjm organization(s): Acquia
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
bkosborne organization(s): Princeton University
acbramley
jibran volunteering organization(s): PreviousNext customer(s): University of Technology, Sydney
jofitz organization(s): ComputerMinds
pwolanin volunteering organization(s): SciShield
generalconsensus organization(s): Forum One
larowlan organization(s): PreviousNext
karenann volunteering
mondrake volunteering
tacituseu
DrupalDude777
catch organization(s): Third and Grove
Pavan B S organization(s): Valuebound
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.