Contribution records
Contributors

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

Give credit to everyone
xjm xjm
lpalgarvio LPCA
jppi_Stu jppi_Stu
servantleader servantleader
binford2k binford2k
jspotswood jspotswood
dmsmidt MrDamasajaga
mdijkstr mdijkstr
kultmarke kultmarke
sw3b sw3b
Anticosti Anticosti
dantz dantz
snsace ssace
saidev saidev
Goulou Goulou
FrequenceBanane FrequenceBanane
danny_joris DannyJoris
Encarte Encarte
tmuras tmuras
tebb Dru-p
David_Rothstein drothstein
shadowmihai shadowmihai
krueschi krueschi
anthonyR anthonyR
Keiichi Keiichi
hclaus hclaus
spam38 spam38
tonycpsu tonycpsu
mhahndl mhahndl
luckystrikerin luckystrikerin
alexbern alexbern
sheila8stamp sheila8stamp
joostvdl joostvdl
paulgemini paulgemini
bjcool bjcool
FireMouse FireMouse
Leeteq Leeteq
marvix marvix
IndieRafael IndieRafael
Bitnetix Bitnetix
stevenovy stevenovy
modstore modstore
jan.koprowski jan.koprowski
Osiris Indriya Osiris Indriya
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.