Contribution records
Contributors

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

Give credit to everyone
TheCrow thecrow
robloach robloach
attiks attiks
greenskin greenskin
laryn laryn
loze loze
jasonsafro JasonSafro
nco71 nco71
nstryker nstryker
shaunak shaunak
Deas Deas
lordsilk lordsilk
blavish blavish
RagsToRich RagsToRich
netentropy netentropy
sun sun
marcvangend marcvangend
Fenwick Fenwick
mawosch mawosch
jamesialford jamesialford
asb asb
pedrorocha pedrorocha
jasont28 jasont28
baalsgate baalsgate
coolhandlukek2 coolhandlukek2
Melissamcewen melissamcewen
benklocek benklocek
fehin fehin
nelslynn nelslynn
volongoto volongoto
Marat Marat
anonymous07 anonymous07
SeanBannister seanbannister
giovanninews giovanninews
mama21mama mama21mama
hongpong HongPong
rneal rneal
dddave dddave
Jerome F Jerome F
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.