Issue
Contribution records
Contributors

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

Give credit to everyone
alex_b
katsikas
ybabel
tauno
webwriter
Funkymoses
arski
Exploratus
infojunkie
iaminawe
parasox
hanno
locomo
yellek
boogsbobo
pdrake
dbritton
andrewlevine
stephenj
joshuajabbour
twistor
primozsusa
Ooxo
lazysoundsystem
Nephele
tayzlor
jdlind38
uwe_a
jeffschuler
clintthayer
johnv
dubs
thedavidmeister
milesw
aaroninaustin
iamc0b
senzaesclusiva
bambilicious
hosais
jdwfly
Encarte
cfennell
vasike
IT100
mry4n
AtlasX
joaomachado
itai_biren
verres
limehouse
prodigeek
dman
victormoya
summit
colan
jamesdixon
shawngo
dakke
asb
ashedryden
chadmkidner
brst t
lunk rat
Renee S
aron novak
R.J. Steinert
Júlio Boaro
mikaoelitiana@gmail.com
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.