Contribution records
Contributors

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

Give credit to everyone
haihachi haihachi
badjava badjava
sophiekovalevsky sophiekovalevsky
kumkum29 kumkum29
hwasem hwasem
edutrul edutrul
drikus drikus
josebc josebc
soubi Soubi
mbawazir mbawazir
JosepJorba JosepJorba
satvision83 satvision83
michaelngodh michael.ngo
edodusi edodusi
gstout gstout
anne1960 anne1960
suldan suldan
Aambro Aambro volunteering
smurfxx smurfxx
phanosd phanosd
duntuk duntuk
sachintyagi99 sachintyagi
bdavy bdavy
hirrando hirrando
mohammed j. razem doublethink
d.sibaud dsibaud
rajab natshah RajabNatshah
Oleksandr Berezko Oleksandr Berezko
Git commit message
Commit types
  • 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

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.