Contribution records
Contributors

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

Give credit to everyone
grienauer Grienauer organization(s): acolono GmbH
FrankT FrankT volunteering
linulo Linulo
Thomas_Zahreddin thomaszahreddin volunteering
achikas jokas
tobiasb tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
Lars_B Lars_B
checker checker
heliogabal heliogabal organization(s): Geeks4Change
hexabinaer hexabinaer volunteering organization(s): hexabinaer customer(s): DGAP
igorski igorski volunteering
reglogge reglogge
anybody Anybody organization(s): DROWL.de
Nortix Nortix
metalbote metalbote volunteering
neffs neffs
spuky spuky volunteering
joachim namyslo horvan volunteering
m-schmitt m-schmitt
chekka.de chekka.de
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.