Issue
Contribution records
Contributors

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

Give credit to everyone
danielveza organization(s): PreviousNext
santanu mondal organization(s): Innoraft
astonvictor volunteering organization(s): Drupal Ukraine Community, DevBranch
smustgrave organization(s): Mobomo
voleger volunteering organization(s): GOLEMS GABB, Drupal Ukraine Community customer(s): Drupal Ukraine Community, GOLEMS GABB
samitk
dcam
nicxvan organization(s): nLightened Development LLC
berdir organization(s): MD Systems GmbH
moshe weitzman
kristiaanvandeneynde organization(s): Tag1 Consulting, Inc.
joachim volunteering
alexpott organization(s): Acro Commerce, Thunder
nod_ organization(s): Très Bien Tech customer(s): Palantir.net, Vardot, OPTASY, OpenSense Labs
sivaji_ganesh_jojodae
longwave organization(s): Full Fat Things
godotislate volunteering
luke.leber volunteering organization(s): Pennsylvania State University
catch organization(s): Third and Grove
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.