Issue
Contribution records
Contributors

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

Give credit to everyone
danepowell
lort
jmuessig
elc
danmed
lordzik
andypost
fen
donquixote
lorlarz2
xjm
StuddMan
juliangb
xmacinfo
DanGarthwaite
jscm
izmeez
pfrenssen
sciencex
ChrisLaFrancis
larowlan
roball
REo
sterndata
ronaldmulero
liquid06
Jbrydolf
fuerst
jbrauer
selfuntitled
pingers
andreic
dstol
cknoebel
keithm
dasjo
schoene_idee
David_Rothstein
Shai
ammaletu
guy_schneerson
x_v
claar
rootwork
fr34ck
lambic
greg.harvey
gábor hojtsy
robin van emden
ñull
gerhard killesreiter
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.