Contribution records
Contributors

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

Give credit to everyone
summit summit
bdragon bdragon
manuj_78 manuj_78
j0rd j0rd
yesct YesCT
scottatdrake scottatdrake
goron goron
zio zio
MattDrupalee MattDrupalee
momper momper
andrewsuth andrewsuth
wilgrace wilgrace
Yorgg Yorgg
socialnicheguru SocialNicheGuru
schvili schvili
ramotowski ramotowski
obiwankaynobi obiwankaynobi
sadist sadist
browlands browlands
cdrichet cdrichet
mayerwin mayerwin
locomo locomo
Golem07 Golem07
kobnim kobnim
homeshop homeshop
asb asb
Stomper Stomper
gman_ gman_git
javdich jman05
khan2ims khan2ims
Digital Storm Digital_Storm
Louis Bob Louis_Bob
toitimhcm toitimhcm
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.