Contribution records
Contributors

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

Give credit to everyone
pillarsdotnet pillarsdotnet
msonnabaum msonnabaum
andrewia andrewia
rmnanney rmnanney
mrharolda haroldmadcap
PedroMiguel PedroMiguel
aspilicious aspilicious
droplet droplet
webchick webchick
Crell Crell
jamesoakley JamesOakley
ROMEO ROMEO
Sylvain_G Sylvain_G
illusionista_86 illusionista_86
kraigory kraigory
marptr marptr
pp pp
coolsandythombare coolsandythombare
amontero amontero
steverweber steverweber
ZiggyQubert ZiggyQubert
heine heine
apotek apotek
sutharsan sutharsan
daffie daffie
damien tournoud damz
archit.lohokare archit.lohokare
pk.long pk.long
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.