Contribution records
Contributors

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

Give credit to everyone
nilocd nilocd
vako vako
mrfelton mrfelton
federico federico
soxofaan soxofaan
DocMartin DocMartin
MBroberg MBroberg
cmoad cmoad
jjchinquist jjchinquist
q0rban q0rban
Pierco Pierco
sinasalek sinasalek
chawl chawl
uno uno
agileware agileware
ianchan ianchan
j2b j2b
cerup cerup
DavidWhite DavidWhite
LeisureLarry LeisureLarry
easp easp
udijw udijw
anon anon
EvanDonovan evandonovan
Avalanche Avalanche
Chad_Dupuis Chad_Dupuis
yakker chrisyakimov
rfay rfay
brokensanity brokensanity
tjmoyer tjmoyer
strae strae
summit summit
tcibah tcibah
anoopjohn anoopjohn organization(s): Zyxware Technologies
Ales Studeny Ales Studeny
curious-trick curious-trick
shane birley shanebirley
R2-D8 heerschlag
Jonah Ellison jonahellison
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.