Contribution records
Contributors

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

Give credit to everyone
tekante tekante
comicsal comicsal
WhiplashInfo WhiplashInfo
berenddeboer berend
webchick webchick
dobrzyns dobrzyns
spacereactor spacereactor
bfroehle bfroehle
Anticosti Anticosti
js js
David_Rothstein drothstein
femrich femrich
blischalk blischalk
rbahaguejr rbahaguejr
rfay rfay
bennash bennash
bdragon bdragon
agileware agileware
rootwork rootwork
damienmckenna damienmckenna
amateescu amateescu
chx chx
xjm xjm
jhedstrom jhedstrom
jamsilver jamsilver
roma7 roma7
webflo webflo
pwolanin pwolanin
kyletaylored KyleTaylored
majdi Majdi
njbarrett njbarrett volunteering
alberto56 alberto56 organization(s): Dcycle
dave reid davereid
yuriy.babenko yuriybabenko
steven jones darthsteven
Jerome F Jerome F
henrijs.seso mansspams
alan d. aland
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.