Contribution records
Contributors

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

Give credit to everyone
bbarunte bbarunte organization(s): Reinblau
Chriz Chriz
Crossfeed Crossfeed
JRopers JRopers
linulo Linulo
Thomas_Zahreddin thomaszahreddin volunteering
tobiasb tobiasb volunteering organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): OpenCulturas e.V.
BaBo BaBo volunteering
bt82 bt82
FrankT FrankT volunteering
hexabinaer hexabinaer organization(s): CoWAIN customer(s): OpenCulturas e.V.
joseffriedrich JosefFriedrich
fisherman90 fisherman90 volunteering organization(s): erdfisch
heliogabal heliogabal organization(s): Geeks4Change
lukzboz lukzboz volunteering
rkoller rkoller
sanduhrs sanduhrs volunteering
joachim namyslo horvan
chekka.de chekka.de
m-schmitt m-schmitt
lomale@bluewin.ch istdp_webmaster volunteering
t.seifert t.seifert
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.