Issue
Contribution records
Contributors

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

Give credit to everyone
gemini
Gidgidonihah
blooksllc
aalexei
asak
Jkello
kenorb
tostinni
stg11
mikeytown2
pkej
finlaycm
farald
vikramy
pjsz
uprojects
mroswell
pvhee
QuangVan
RoboPhred
foodbo
excaliburst
LEternity
stkrzysiak
playfulwolf
andrii_svirin
Yura
vacilando
Grayside
visceroid
rootwork
roball
vladsavitsky
loophole080
gabor_h
summit
Headache
brycesenz
corbacho
ahtih
Moonshine
MacaroniDuck
YK85
khalor
maedi
amal850720
wizonesolutions
frakke
truyenle
cphilli12
colan
Ares_ekb
Wouter Van den Bosch
Jorge-2
aren cambre
geek-merlin
ari-meetai
amir simantov
vertikal.dk
XiaN Vizjereij
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.