Contribution records
Draft
Contributors

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

Give credit to everyone
miro_dietiker mirodietiker organization(s): MD Systems GmbH
jonathanshaw jonathanjfshaw
yobottehg yobottehg
berdir berdir organization(s): MD Systems GmbH
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
zmove zmove
ciss ciss volunteering
mdroste meinolf
vollepeer vollepeer organization(s): AmeXio Fuse
kevinquillen kevinquillen organization(s): Velir
johnchque yongt9412 organization(s): MD Systems GmbH
drobnjak drobnjak organization(s): MD Systems GmbH
patrickroma patrickroma
sgurlt sgurlt volunteering organization(s): Bright Solutions GmbH
primsi primsi organization(s): MD Systems GmbH customer(s): MD Systems GmbH
lyalyuk lyalyuk organization(s): AnyforSoft customer(s): AnyforSoft
strykaizer StryKaizer volunteering organization(s): ClicketyClick
jurriaanroelofs peach organization(s): DXPR
ckng ckng volunteering
RAFA3L RAFA3L
batkor batkor
shaisamuel shaisamuel
jeroen.b jeroen.b organization(s): .VDMi/
james.williams jameswilliams organization(s): ComputerMinds
simon georges simongeorges organization(s): Makina Corpus
jepster_ jepSter
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.