Contribution records
Contributors

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

Give credit to everyone
jeremyluby jeremyluby
tresero tresero
piwchix piwchix
jh3 ejh3
DanishK DanishK
dddave dddave
mostoneskin mostoneskin
clcanela clcanela
aasarava aasarava
rlmumford rlmumford
wheatpenny wheatpenny
obstikle obstikle
czigor czigor
ronny89 ronny89
rayvan rayvan
d2ev d2ev
sbree sbree
deviantintegral deviantintegral
russellb russellb
onehandsomedog onehandsomedog
amontero amontero
christophrumpel christophrumpel
davidneedham davidneedham
micnap micnap
i_rice i_rice
glamdring glamdring
bentleychan bentleychan
pradeep22saini pradeep22saini
Mohva Mohva
heyehren kleinermann
spgd01 spgd01
jathoo jathoo
nateb nateB
markie markie organization(s): Current
guidot guidot
rivimey rivimey
samheuck emuSHack volunteering
Vemma-1 Vemma-1
Swarnendu-Dutta Swarnendu-Dutta volunteering
justmagicmaria JustMagicMaria
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.