Contribution records
Contributors

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

Give credit to everyone
mrmeech mrmeech
jboeger jboeger
ianreeves ianreeves
NoRandom NoRandom
kahunacohen kahunacohen
wiifm wiifm
caraiba caraiba
filiptc filiptc
kaakuu kaakuu
jeffreyvddb jeffreyvddb
MadOverlord MadOverlord
eddie123123 eddie123123
zwhalen zwhalen
anarcat anarcat
drein drein
edcazini EdCazini
HelloStephanie HelloStephanie
andread AndreaD
ZyanKLee ZyanKLee
betz betz
mossill mossill
fattmox fattmox
candygirl777 candygirl777
djinc01 djinc01
Gilneas Gilneas
naught101 naught101
michaek michaek
venusrising venusrising
Vector9 Vector9
neorg neorg
steinmb steinmb
juampynr juampy
aren cambre arencambre
danny englander danny-englander
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.