Contribution records
Contributors

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

Give credit to everyone
johns996 johns996
jcisio jcisio
kazar kazar
sashkernel sashkernel
wwalc wwalc
wooody wooody
wranvaud wranvaud
meno1max meno1max
NicoDruif NicoDruif
taran2l Taran2L
bdombro bdombro
sunnykasera3107 sunnykasera3107
jwillard jwillard
Noyz Noyz
mattzhou7 mattzhou7
corbin corbin
pilotget pilotget
EcoFin EcoFin
emmonsaz emmonsaz
fraxinus fraxinus
nattyweb NattyWebDev
jakwong jakwong
Rob_Feature bobchristenson
Xrobak Xrobak
mklprasanna mklprasanna
Trey Trey
rajeevkumar rajeevkumar
shamsher_alam shamsher327
MtRoxx MtRoxx volunteering
raj45 raj45
firoz2456 firoz.sabaliya volunteering
berenddeboer berend
lrodarte lrodarte
John Carbone JohnCarbone
E Johnson E_Johnson
chadwick wood wickamos
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.