Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
marcoscano organization(s): MD Systems GmbH
damienmckenna organization(s): Current
seanb
berdir organization(s): MD Systems GmbH
mbovan organization(s): MD Systems GmbH
devkinetic
reszli organization(s): Dropsolid
radelson organization(s): WebstanZ
kmani
bbu23 organization(s): Ninja Coders
bceyssens organization(s): TIRO BV
igork96 organization(s): X Gate
urvashi_vora organization(s): Valuebound customer(s): Valuebound
kburakozdemir volunteering organization(s): binbiriz
millerrs
kriboogh
p4trizio organization(s): Elicos
randalv volunteering
thijsv
squinternata
bohus ulrych
louis-cuny organization(s): Daille-daille
baikho volunteering organization(s): iO
tcrawford
tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
mably organization(s): Bordeaux Metropole
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.