Contribution records
Draft
Contributors

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

Give credit to everyone
Rob_Feature bobchristenson
bennos bennos
iNade iNade
butler360 butler360
gausarts gausarts
reptilo reptilo
harcher hga77
joshuautley joshuautley
radj radj
ahimsauzi ahimsauzi
danryan danryan
BeaPower BeaPower
shriji shriji
ccshannon ccshannon
bearstar bearstar
rwt rwt
zlorro zlorro
AdrianB AdrianB
AniaMi AniaMi
lefko lefko
verta verta
Funksmaname Funksmaname
izmeez izmeez
metalshreds metalshreds
brenes brenes
wheck wheck
roball roball
glasswool glasswool
net_runner Net_Runner
kobnim kobnim
akolahi akolahi
slimgrin SlimGrin
Stuart Greenfield stuartgreenfield
design.er stefanriske
rob c robc
david stosik davidstosik
djudd djudd
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.