Contribution records
Contributors

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

Give credit to everyone
jmiccolis jmiccolis
soxofaan soxofaan
nedjo nedjo
aschiwi aschiwi
scothiam scothiam
alberto56 alberto56
alphageekboy alphageekboy
samhassell samhassell
neurojavi neurojavi
jec006 jec006
pwhiteside pwhiteside
scottrigby scottrigby
ao2 ao2
SebCorbin sebcorbin
crabsoul rashmi08
jdleonard jdleonard
akalam desarrollo2.0
joachim joachim
wundo wundo
vincenzodb vincenzodb
hefox hefox
pachabhaiya pachabhaiya
jastraat jastraat
rjacobs rjacobs
Josh Benner joshbenner
patty.fresonke patty.fresonke
geek-merlin geek-merlin
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.