Contribution records
Draft
Contributors

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

Give credit to everyone
karens karens
q0rban q0rban
Grayside grayside
steinmb steinmb
randallknutson randallknutson
nedjo nedjo
paulmckibben paulmckibben
rcross rcross
safetypin mcowgur
pmackay pmackay
alfthecat AlfTheCat
fabianx Fabianx
sanduhrs sanduhrs
uberellis mordrack
mrfelton mrfelton
socialnicheguru SocialNicheGuru
batje batje
13rac1 eosrei
hefox hefox
stoickthevast techwarrior
babbage babbage
mpotter mpotter
mrf mrf
basvredeling basvredeling
GaryDev GaryDev
jenlampton jenlampton
subhojit777 subhojit777
tripper54 tripper54
jcisio jcisio
hargobind hargobind
daddison daddison
RyanPrice RyanPriceDotCa
gram.steve sg3524
drew reece drew_reece
maciej lukianski maciej.lukianski
Gemma Morton GregMcKeen
Jan van Diepen janvandiepen
greg.1.anderson greg1anderson
brad.bulger brad.bulger
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.