Issue
Contribution records
Contributors

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

Give credit to everyone
BenK
will_in_wi
jeffl8n
hadsie
dgastudio
kinshuksunil
chriz001
ccheu
mehtatejas
kissinger
idiotprayer
sw3b
gvc
nevergone
lesleyfernandes
off
jeffwidman
hendrakieran
yugongtian
starsinmypockets
hypertext200
likewhoa
whyn0t
theullrich
rogical
Hazeltree
Fidelix
kolobok38
halloffame
sslider999
hgroover
Taxoman
milorand
dddbbb
medden
gillarf
jamiegotluckies
pancrilio
crispinbailey
davycw
orendain
funkju
andrenoronha
jg352
mefisto75
hubScrappy
Refineo
ehmprah
dannyjohnson1
chris_boudreaux
mototribe
paul_constantine
jenlampton
scripthead
nagiek
josephpnc
mgifford
glekli
junkerjp
smk-ka
Geeky Lass
Håvard
Carlos Miranda Levy
Andy B
frank.schram
william.lai
dorien
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.