Issue
Contribution records
Contributors

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

Give credit to everyone
chazz
rgraves
samhassell
bbeyer
xcorex
apersaud
rodneireis
JohnColeman
rout
nicktech
espirates
luigithekid
rhlowe
crutch
quicksketch
brian_c
j0k3z
ymmatt
davidps
vernond
iantresman
vedeem
MarkFischer
jh3
francoud
hanoii
hovel
jeremyll
jumoke
YK85
Mamoun
pizzapotamus
Kreativs
kriskhaira
benjohnson
dbravender
calculus
kingandy
bluepuma
infringer
osha
chrisgross
bkosborne
saulg
csilfverduk
slefevre1
jrockowitz
fourthandvine
bcweaver
derpasaurus
mradcliffe
orces
mrdorylek
twooten
anithegregorian
osman
finedesign
elpino
vaibhav_jadia
billp44ruby
lykyd
marcvangend
watergate
ladybug_3777
danchadwick
mrgoodfellow
ElineK
jack.r.abbit
El Bandito
diego.nava
Dot-Communications
sense-design
Greg Turner
magnetic marketing
chris.jichen
Thing.Doer
nagchampa
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.