Contribution records
Contributors

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

Give credit to everyone
mfer mfer
JacobSingh JacobSingh
Jackinloadup Jackinloadup
effulgentsia effulgentsia
aaron aaron
iko iko
nirbhasa nirbhasa
ogi ogi
lelizondo lelizondo
webankit babbar.ankit
arthurf arthuregg
thomas4019 thomas4019
presleyd presleyd
jeffwidman jeffwidman
AndrzejG AndrzejG
neurojavi neurojavi
anavarre anavarre
dlumberg dlumberg
marcvangend marcvangend
sanderjp sanderjp
good_man goodman
RonP RonP
safetypin mcowgur
hnln HnLn
rickvug rickvug
CrashNet CrashNet
g76 g76
achton achton
aspilicious aspilicious
keha3912 keha3912
webflo webflo
cpelham cpelham
TripX TripX
kingjohnnet kingjohnnet
ZuluWarrior ZuluWarrior
puidu puidu
axe312 axe312
djanousek djanousek
Niklas Fiekas niklas
das-peter daspeter
dave reid davereid
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.