Contribution records
Contributors

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

Give credit to everyone
mschupan mschupan
salvis salvis
benracer benracer
pdcarto patdunlavey
TrinitySEM TrinitySEM
fago fago
innovative95 innovative95
xingwang xingwang
artbody artbody
emdalton emdalton
webwriter webwriter
particle particle
seovegasrich seovegasrich
webchick webchick
liquidcms liquidcms
husztisanyi husztisanyi
BradM BradM
ClearXS ClearXS
kayusee kayusee
sparkweb sparkweb
majorrobot majorrobot
Encarte Encarte
krisrobinson krisrobinson
BenWrighton BenWrighton
gdf gdf
gthing gthing
good_man goodman
bsandor bsandor
munyiva munyiva
shabbir Shabbir
chaplin.matt chaplin.matt
kims kims
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.