Contribution records
Contributors

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

Give credit to everyone
irtech irtech
karens karens
vito_a vitoa
markDrupal markdrupal
arlinsandbulte arlinsandbulte
markfoodyburton markfoodyburton
KoCo KoCo
gmclelland gmclelland
geerlingguy geerlingguy
rgmpac rgmpac
jeffschuler jeffschuler
NukeHavoc NukeHavoc
Spark_man Spark_man
webwriter webwriter
somanyfish somanyfish
YK85 YK85
grasmash madmatter23
nkschaefer nkschaefer
seaneffel seaneffel
brightbold brightbold
mrharolda haroldmadcap
damienmckenna damienmckenna organization(s): Current
aron novak aronnovak
developer-x developerx
tim.plunkett tim.plunkett
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.