Contribution records
Contributors

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

Give credit to everyone
klausi klausi organization(s): jobiqo - job board technology
BerndB BerndB volunteering
trothe trothe
fisherman90 fisherman90 volunteering organization(s): erdfisch
fholldorff fholldorff organization(s): erdfisch
hexabinaer hexabinaer volunteering
MethodJules MethodJules
jjchinquist jjchinquist organization(s): drunomics
jurgenhaas jurgenhaas organization(s): bitegra Solutions, LakeDrops
hydra Hydra volunteering
al3nka al3nka
katzilla katzilla organization(s): Reinblau
snable cschnabl volunteering organization(s): 42robots
drupallerina drupallerina
rkoller rkoller
danielspeicher danielspeicher organization(s): bitegra Solutions
fhaeberle haeberle organization(s): bitegra Solutions, PARAGON Executive Services GmbH
grienauer Grienauer volunteering organization(s): acolono GmbH
criz criz organization(s): acolono GmbH
norman.lol koiwo organization(s): 1xINTERNET
joachim namyslo horvan
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.