Contribution records
Contributors

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

Give credit to everyone
wundo wundo
markhalliwell markcarver
olamaekle olamaekle
laogui laogui
zmove zmove
wormz30 wormz30
philbar philbar
rokr rokr
el7cosmos el7cosmos
kslonka kslonka
TheJoker TheJoker
heylookalive alliprice
JakeWilund JakeWilund
kmadel kmadel
webindustries webindustries
anavarre anavarre
jojototh mogdesign
tr33m4n tr33m4n
Argus Argus
valkum valkum
robloach robloach
AlfredK AlfredK
ComboPrime ComboPrime
bryancasler animelion
herom herom
rerooting rerooting
charlie charles charlie_charles
David de Vicente David_de_Vicente
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.