Issue
Contribution records
Contributors

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

Give credit to everyone
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
borisson_ volunteering organization(s): Calibrate
catch organization(s): Third and Grove
alexpott organization(s): Acro Commerce, Thunder
berdir organization(s): MD Systems GmbH
peximo organization(s): Tag1 Consulting, Inc.
cgoffin organization(s): Sopra Steria
fabio84 organization(s): Cimatti Consulting
francescoq
pandaski organization(s): govCMS (Australian Government Department of Finance)
scuba_fly organization(s): ronder
rachel_norfolk organization(s): Drupal Association
init90 organization(s): Drupal Ukraine Community, ZANZARRA Drupal Agency
jungle volunteering
vctlzac
mr.baileys organization(s): SQLI - Belgium
petr illek volunteering organization(s): Annertech
neslee canil pinto
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.