Issue
Contribution records
Contributors

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

Give credit to everyone
anrikun
anruether
rothatboat
altbzh
davidpauljunior
Tafa
tescometro
unc0nnected
soulston
knigh7
iaminawe
damiandab
jrabeemer
itzcoatl
ayalon
jydrupal
tivie
leewebdev
thomasgm
krisrobinson
temelkoff
nelsonbranco
hihappycats
vaudaville
narongwit12
SchwebDesign
iamjon
heli0s
demonrage
sjohnson
aegagros
peterbrunton
extensive
antiorario
ilgriso
ifrik
galactus
Macronomicus
wmfinck
BeaPower
Sk8erPeter
nnotario
zeropx
muddie
fuzzyjared
jerry
dkingofpa
brycesenz
dale42
sirian
amanda
duntuk
aaron
purna_dey
_sparrow_
zisser
the_g_bomb
alex ua
John Carbone
green monkey
Vc Developer
gettysburger
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.