Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rmiddle
unarsu
puleddu
wuf31
jweberg
chasz
Mathews_1
panji
darumaki
monsterweb
hutch
phicarre
nancydru
zoia
ahkiam
asak
kelvinwong
rachel_norfolk
adam_b
bcobin
jordanmagnuson
fred0
cside
ck9
ianchan
helenj
Apollo610
israelshmueli
kiwi_steve
eurekaloop
chrism2671
bomarmonk
chrispy
lejon
solipsist
robin1988
crazzykiwi
darwinjd
a_c_m
Observer123
HS
renoproc
verta
doomed
GuanoApe
fossle
leob
BenK
mahfuz0
lias
Prasad Shir
i.chris.jacob
Katrina B
Dr Jay
manuel.solis
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.