Contribution records
Contributors

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

Give credit to everyone
yochee yochee
CinemaSaville CinemaSaville
lifepillar lifepillar
effulgentsia effulgentsia
JacobSingh JacobSingh
likewhoa likewhoa
jerodfritz the7thsim
iko iko
cartagena cartagena
Jose_ibi Jose_ibi
Jackinloadup Jackinloadup
kaluchkin kaluchkin
mightyiam mightyiam
TripX TripX
Taxoman Taxoman
ParisLiakos rootatwc
3rdLOF kannary
sun sun
idflood idflood
CarelessChaser CarelessChaser
becw bec
muschpusch muschpusch
robeano robeano
CrashNet CrashNet
bryancasler animelion
ddanier ddanier
ZuluWarrior ZuluWarrior
codesmith codesmith
jrabeemer Giovanni_Glass
aaron aaron
luksak luksak
tsvenson tsvenson
arthurf arthuregg
johnpitcairn johnpitcairn
lsolesen lsolesen
redndahead redndahead
mrfelton mrfelton
avolve avolve
jacobroufa jacobroufa
Scott J ScottJ
das-peter daspeter
dave reid davereid
james.elliott jameselliott
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.