Issue
Contribution records
Contributors

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

Give credit to everyone
DocuAnt
catch
berdir
geerlingguy
dealancer
drynok
klausi
tsvenson
rbayliss
xjm organization(s): xjm
interx
dries
bfroehle
indytechcook
chx
andypost volunteering organization(s): Skilld
adnasa
joestewart
oriol_e9g
sun
David_Rothstein volunteering
amyhribar
Uzo
valthebald
Letharion
fabianx volunteering organization(s): Tag1 Consulting, Inc.
yoroy
yesct
cosmicdreams
anon
johnv
fstrevisan_eZly
grimreaper
matslats volunteering
lpalgarvio
cweagans organization(s): NBCUniversal
sutharsan
aerozeppelin organization(s): California State University San Bernardino
ugintl
jollysolutions
quietone organization(s): PreviousNext
mariusz.slonina
David D
damien tournoud
gábor hojtsy
tim.plunkett
Tor Arne Thune
Paul B
hass
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.