Issue
Contribution records
Contributors

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

Give credit to everyone
M_Hirschpiel organization(s): Nodegard
anybody organization(s): DROWL.de
Danic
FrankT volunteering
PTJ
Thomas_Zahreddin volunteering
katissima
reglogge
rkoller
salvis
tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): publicplan GmbH
joseffriedrich
linulo
Loredo
pancho volunteering
bt82
hexabinaer volunteering
igorski volunteering
katzilla organization(s): Reinblau
nerdoc
choy volunteering
Flipperx
matslats
metalbote volunteering
seppelM
triple5 volunteering
joachim namyslo
c-logemann organization(s): Nodegard
m-schmitt
samuel schnell
Walter.Kuhn volunteering
chekka.de
eric heydrich organization(s): werbeagentur kartinka gmbh & co. kg
kai.stampe@gmail.com
Git commit message
Commit types
  • 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

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.