Contribution records
Draft
Contributors

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

Give credit to everyone
mattbk mattbk
murrdogg murrdogg
dudelookslikealady dudelookslikealady
XerraX XerraX
augsburgde augsburgde
Saler Saler
denni denni
SuperZambezi SuperZambezi
oeaton oeaton
salvatoren ๐Ÿ‡ฎ๐Ÿ‡น salvatoren
sinasalek sinasalek
marazmus marazmus
ndstate ndstate
vb vb
jawatkin jawatkin
chawl chawl
dzhu dzhu
eitai2001 eitai2001
System6Hosting System6Hosting
pomakk pomakk
Raitsa Raitsa
robxu9 robxu9
wiciu wiciu
Observer123 Observer123
hernani hernani
abx abx
fatcrobat fatcrobat
Fidelix Fidelix
bryancasler animelion
drumfreak drumfreak
reader6911 reader6911
penyaskito penyaskito
leahmd purplefizz
Tolas Tolas
Josiv Josiv
thegoof thegoof
cepiat cepiat
Unlimited Unlimited
gumdrop gumdrop
edsel soul_Jah
Real Digger Real_Digger
joachim namyslo horvan
MOD JASON MOD_JASON
psiegel psiegel
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.