Contribution records
Contributors

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

Give credit to everyone
jjchinquist jjchinquist organization(s): drunomics, Drupal Austria
alexj12 Alexj12 organization(s): Zoocha
antonellasevero antonellasevero
artusamak Artusamak
dan2k3k4 dan2k3k4 organization(s): Amazee Labs
foka_patrick foka_patrick volunteering
hansa11 hansa11 organization(s): Ramsalt Lab
jannekalliola jannekalliola organization(s): Exove
jennydumitrescu jennydumitrescu organization(s): University of Cambridge
kpolte kpolte
mon_franco mon_franco organization(s): NTT DATA
nico_kuoni nico_kuoni
rachel_norfolk rachel_norfolk volunteering organization(s): Cambridge University Press & Assessment
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
vulcanr vulcanr volunteering organization(s): Annertech
fedor.lukianov fedor.lukianov
issa.haddadin issahh 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.