Issue
Contribution records
Contributors

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

Give credit to everyone
pillarsdotnet
pasqualle
dmitrig01
vthirteen
AlexisWilke
crea
marcoBauli
seanr
bcobin
jbrauer
japerry
Chad_Dupuis
darkoba
SeanBannister
alison
ericm
mikeytown2
brightbold
micheleannj
jbeall
Sborsody
escoles
opteronmx
zarko
protoplasm
cels
thaddeusmt
danny_joris
sangus
joshmiller
bstrange
AdrianB
xerexes
srobert72
sapiusenator
giorgosk
jrtorrent
jannalexx
stijnbe
montag
jibbajabba
Ron_WI
valante
dig1
kenorb
acrollet
gooddesignusa
bleen
pwolanin
donquixote
mcurry
calefilm
mattew
petertj
mvc
keith.smith
dave reid
damien tournoud
tim.plunkett
Alan.Guggenheim
Jerome F
Rob T
ar-jan
mariano.barcia
chris-ju
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.