Contribution records
Contributors

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

Give credit to everyone
achikas jokas
dddave dddave
FrankT FrankT volunteering
linulo Linulo
Thomas_Zahreddin thomaszahreddin volunteering
tobiasb tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): OpenCulturas e.V.
AndreU AndreU
anybody Anybody organization(s): DROWL.de
bt82 bt82
hexabinaer hexabinaer organization(s): CoWAIN customer(s): OpenCulturas e.V.
reglogge reglogge
slowflyer slowflyer
aschiwi aschiwi organization(s): undpaul
broon broon
igorski igorski
metalbote metalbote volunteering
rkoller rkoller
rmeissner rmeissner
ThomasK ThomasK
pasqualle pasqualle volunteering
joachim namyslo horvan
m-schmitt m-schmitt
jepster_ jepSter organization(s): publicplan GmbH
Walter.Kuhn Walter.Kuhn volunteering
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.