Contribution records
Contributors

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

Give credit to everyone
steinmb steinmb
ademarco ademarco
BenK benk
vlooivlerke vlooivlerke_git
dgastudio kervi
ccardea ccardea
rocbrook rocbrook
combicart combicart
botris botris
hlykos hlykos
mcaden mcaden
bels bels
jhedstrom jhedstrom
generalconsensus generalconsensus
jlporter jlporter
aristeides aristeides
mksweet mksweet
nikeev AntNick
j0k3z j0k3z
entrigan entrigan
michaelfavia michaelfavia
pol Pol
Yorgg Yorgg
jherencia jherencia
goldenboy goldenboy
nessollo nessollo
ben kuper benkuper
Adam S Adam_S
Karsten.S Karsten.S
Stefan Haas Stefan_Haas
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.