Contribution records
Contributors

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

Give credit to everyone
mmbk mmbk volunteering organization(s): erdfisch
al3nka al3nka
MethodJules MethodJules
cawi cawi volunteering
danielspeicher danielspeicher
atropoides Atropoides volunteering
stolzenhain stolzenhain
veralorenzi veralorenzi organization(s): Liip
dan2k3k4 dan2k3k4 organization(s): Amazee Labs
pminf pminf
maacl maacl
jurgenhaas jurgenhaas organization(s): LakeDrops
rkoller rkoller
bircher bircher volunteering organization(s): Nuvole
drupalfan2 drupalfan2 volunteering
fholldorff fholldorff organization(s): erdfisch
asishsajeev asishsajeev organization(s): Material
grienauer Grienauer volunteering organization(s): acolono GmbH
a.milkovsky milkovsky organization(s): Drupal Austria, k-digital
Tilo Schumann Tilo_Schumann
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.