Contribution records
Contributors

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

Give credit to everyone
highvoltage highvoltage
yhahn yhahn
jhedstrom jhedstrom
Wappie08 Wappie08
damienmckenna damienmckenna
Stalski stalski
joachim joachim
hedac hedac
seanberto seanberto
michaellander michaellander
safetypin mcowgur
himerus himerus
scor scor
joostvdl joostvdl
febbraro febbraro
acouch acouch
justafish justafish
franz franz
klim_ klim
iorgos iorgos
ggevalt ggevalt
picxelplay picxelplay
sp3boy sp3boy
Encarte Encarte
marcus178 marcus178
steinmb steinmb
fxarte fxarte
zkrebs zkrebs
chinita7 chinita7
RavinderChopra RavinderChopra
greggles greggles
aaronbauman aaronbauman
dercheffe dercheffe
metallized sergiomeneses
webel webel
nedjo nedjo organization(s): Drutopia
steven jones darthsteven
finn lewis ecofinn
danny englander danny-englander
sheldon rampton sheldon
Tomáš Fejfar Tomas_Fejfar
k-mo Mo-k-tec
ludo.r dolu
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.