Contribution records
Contributors

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

Give credit to everyone
Dimm dimm
quicksketch quicksketch
BrightLoudNoise brightloudnoise
vipconsult vipconsult
dopry dopry
anantagati anantagati
Tim99 Tim99
OpenChimp OpenChimp
yeeloon yeeloon
jpetso jpetso
poilf poilf
psynaptic psynaptic
George2 george2
capitano83 capitano83
pingers pingers
Farreres Farreres
dman dman
sgriffin sgriffin
avolve avolve
jdevries jdevries
TC44 TC44
psicomante psicomante
stella stella
mw4ll4c3 mw4ll4c3
texas-bronius bronius
Christopher Herberte chrisherberte
z.stolar zstolar
Antoine Lafontaine antoinelafontaine
unrev.org unrev.org
mir-ink mir-ink
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.