Contribution records
Contributors

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

Give credit to everyone
johnv johnv
7wonders 7wonders
eiriksm eiriksm
summit summit
ts145nera ts145nera
technikh nikhildubbaka
itamair itamair
philipz philipz
nmc nmc
reszli reszli
Masala Masala
imiksu iMiksu
twistor twistor volunteering
davident davident
sin sin
ryumkin ryumkin
kovaski kovaski
westie westie
Frando frando
asutton asutton
Andrey Zakharov Andrey_Zakharov
XiaN Vizjereij XiaN
Steven.Pescador SAF13
tyler-durden tyler-durden
gaëlg gaelg
geek-merlin geek-merlin
David Hernández David_Hernandez
m.stenta mstenta
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.