Contribution records
Contributors

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

Give credit to everyone
FrankT FrankT volunteering
Joa Joa
linulo Linulo
Thomas_Zahreddin thomaszahreddin volunteering
achikas jokas
rkoller rkoller
spuky spuky volunteering
tobiasb tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
anybody Anybody organization(s): DROWL.de
berdir berdir organization(s): MD Systems GmbH
Loredo Loredo
checker checker
ckaotik ckaotik organization(s): werk21
criz criz organization(s): acolono GmbH
dp85 dp85
gngn gngn organization(s): Computer Manufaktur GmbH
slowflyer slowflyer
hexabinaer hexabinaer volunteering organization(s): hexabinaer customer(s): DGAP
joachim namyslo horvan volunteering
samuel schnell samuel schnell
m-schmitt m-schmitt
Walter.Kuhn Walter.Kuhn
chekka.de chekka.de
thomas.frobieter thomas.frobieter
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.