Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
johnwebdev organization(s): Kodamera AB
berdir organization(s): MD Systems GmbH
kevincrafts
tedbow organization(s): Acquia
amateescu customer(s): Pfizer, Inc.
damienmckenna organization(s): Current
jibran volunteering
twfahey volunteering organization(s): University of Texas at Austin
sjerdo volunteering organization(s): Synetic
eclipsegc organization(s): Acquia
aaronmchale organization(s): The University of Edinburgh
johnzzon organization(s): Kodamera AB
alexpott organization(s): Thunder
mglaman organization(s): Centarro
phenaproxima organization(s): Acquia
mtodor organization(s): Thunder
japerry
xjm organization(s): Acquia
bkosborne volunteering organization(s): Princeton University
yanniboi organization(s): FreelyGive
mpotter organization(s): Phase2
webchick organization(s): Acquia
alesr
samuel.mortenson organization(s): Acquia
hawkeye.twolf organization(s): Kalamuna
tim.plunkett organization(s): Acquia
tim bozeman organization(s): Bozeman.Engineering customer(s): Achieve Internet
gábor hojtsy organization(s): Acquia
r_h-l
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.