Contribution records
Contributors

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

Give credit to everyone
rj rj
matt_paz mattpaz
seaneffel seaneffel
nnn nnn
tamasd yorirou
drewish drewish
brianbrown brianbrown
guillaumeduveau guix
mjhammel mjhammel
bcobin bcobin
rmiddle rmiddle
jacobson jacobson
annajonna annajonna
Th30philus Th30philus
chalkboard chalkboard
mlconnor mlconnor
abi2 abi2
tobiberlin tobiberlin
jmagunia jmagunia
likewhoa likewhoa
caiosba caiosba
aasarava aasarava
yogeshchaugule8 yogeshchaugule
dgtlmoon dgtlmoon
esbon esbon
mattwmc mattwmc
maximpodorov maximpodorov
zach harkey zachharkey
Justin Freeman greenrenault
manuel.adan adan
Git commit message
Commit types
  • 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

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.