Issue
Contribution records
Contributors

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

Give credit to everyone
merlinofchaos
manogolf
timwood
Vote_Sizing_Steve
Melissamcewen
rumblewand
jackbravo
djh007
spineless
rootwork
Letharion
jwilson3
bulldozer2003
tygbiten
AndreyMukha
wimberb
richH
helmo volunteering organization(s): Initfour websolutions
damienmckenna organization(s): Current
skimi
rajmataj
jenlampton organization(s): Jeneration Web Development customer(s): Dog Star Daily
jonraedeke
rivimey volunteering
izmeez
webt
japerry organization(s): Acquia
jelo
brooke_heaton
wj-2
Renee S
clemens.tolboom volunteering
hawkeye.twolf organization(s): Kalamuna
bomarmonk
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.