Contribution records
Contributors

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

Give credit to everyone
fischerj fischerj
jwgreen1974 jwgreen1974
picapaoo picapaoo
grobemo grobemo
xhochy xhochy
capmex capmex
leon85321 leon85321
fago fago
tryitonce tryitonce
jvieille jvieille
duozersk duozersk
TSE TSE
akalsey akalsey
wdevn wdevn
swordedge swordedge
CarbonPig CarbonPig
danny_joris DannyJoris
salvis salvis
andread AndreaD
anewbie anewbie
pepó pepo
avf avf
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.