Issue
Contribution records
Contributors

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

Give credit to everyone
gdd
andypost
chx
jacine
seanr
afox
wroxbox
heather
yched
lsmith77
robloach
tlattimore
Crell
webchick
fabpot
dww
mortendk
swentel
gravelpot
Brandonian
nonsie
ebeyrent
jyve
dodorama
janusman
dvessel
glennpratt
rudiedirkx
AmyStephen
pixelwhip
jessebeach
eigentor
c4rl
zviryatko
phoenix
TransitionKojo
opi
pazhyn
n8tron
cosmicdreams
gh2012
wjaspers
dcmouyard
zigmoo
David_Rothstein
neclimdul
danielhonrade
jide
karens
gkatsanos
peterx
nicl
geerlingguy
jenlampton
Grayside
pixelmord
okwari
philippejadin
bojanz
bsmirnov
effulgentsia
fuzzy76
plach
jeebsuk
dreamleaf
dozymoe
zirafa
cweagans
ry5n
timmillwood
troyer
fmizzell
dries
sphism
thijsvdv
RobW
ethanw
kbell
steveoliver
podarok
jwilson3
sun
rene bakx
moshe weitzman
dustin@pi
tim.plunkett
owen barton
Graeme Blackwood
star-szr
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.