Issue
Contribution records
Contributors

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

Give credit to everyone
pillarsdotnet
catch
webchick
carlos8f
yched
bojanz
mile23
tpopham
steinmb
fago
johnpitcairn
xjm
David_Rothstein
joachim
karens
michelle
Bojhan
dqd
klonos
yesct
sun
agentrickard
Crell
plach
chx
effulgentsia
dries
gdd
Madis
fubhy
xmacinfo
swentel
damienmckenna
jenlampton
arlinsandbulte
pounard
tsvenson
yoroy
amateescu
pancho
fmizzell
mikeryan
dkre
thedavidmeister
berdir
andypost
dawehner
alexpott
falcon03
ParisLiakos
mtift
StuartJNCC
pwolanin
tstoeckler
mradcliffe
drumm
gokulnk organization(s): Azri Solutions
moshe weitzman
sylvain lecoy
tim.plunkett
greg.1.anderson
Mołot
owen barton
star-szr
gábor hojtsy
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.