Contribution records
Contributors

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

Give credit to everyone
BluesmanEP BluesmanEP
ardas duke
spopovits spopovits
apollonet apollonet
Lappie Lappie
Wutimer DavidW
dmendez dmendez
motto motto
francewhoa Francewhoa
jefbak2 jefbak2
joshmiller joshmiller
wallbay1 wallbay1
raymo raymo
mk1000 mk1000
marcp marcp
andrewfn andrewfn
the1who the1who
perandre perandre
borisbarowski borisbarowski
cgjohnson cgjohnson
geodaniel geodaniel
prodosh pban02
webengr webengr
mhartman2009 mhartman2009
matt b Matt_B
Rob T Rob_T
Michael Phipps michaelphipps
Anusha Isaacraj Anusha_Isaacraj
paulnem paulnem
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.