Contribution records
Draft
Contributors

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

Give credit to everyone
computer_jin computer_jin
keesee CorpX
yngvewb yngvewb
brisath brisath
autoberater autoberater
szy szy
summit summit
boabjohn boabjohn
gavin_o gavin_o
askibinski askibinski
fabiavmz fabiavmz
ehikr ehikr
ice5nake ice5nake
Freakachoo Freakachoo
hanspln hanspln
sunchaser sunchaser
couloir007 couloir007
Gessle Gessle
hillaryneaf nektir
Mika Heineken Mika_Heineken
Carlos Miranda Levy carlosmirandalevy
Frederic wbase frederic_coworks
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.