Contribution records
Contributors

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

Give credit to everyone
joachim joachim volunteering
mtodor mtodor organization(s): Thunder
primsi primsi organization(s): MD Systems GmbH customer(s): MD Systems GmbH
slashrsm slashrsm organization(s): MD Systems GmbH
paranojik paranojik organization(s): Amazee Labs
imclean imclean
juanramonperez juanramonperez volunteering
Tahanima Tahanima
jungle jungle volunteering
podarok podarok organization(s): Drupal Ukraine Community, ITCare, Open Y customer(s): Drupal Ukraine Community, Open Y
chr.fritsch chr.fritsch organization(s): Thunder
stefanos.petrakis stefanos.petrakis volunteering organization(s): PwC's Experience Center
samuel.mortenson samuel.mortenson organization(s): Acquia
a.milkovsky milkovsky organization(s): Styria Digital Services
ñull com2 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.