Issue
Contribution records
Contributors

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

Give credit to everyone
nick_vh organization(s): Dropsolid
taran2l organization(s): Lemberg Solutions
agentrickard organization(s): Palantir.net
andypost volunteering organization(s): Skilld
hestenet organization(s): Drupal Association
mglaman organization(s): Bluehorn Digital
mirom organization(s): Czech Drupal Association, Slovak Drupal Association
rachel_norfolk organization(s): Drupal Association
rteijeiro organization(s): Youpal Group
xjm organization(s): Acquia
Mixologic organization(s): Drupal Association
mikelutz volunteering organization(s): Four Kitchens
gábor hojtsy organization(s): Acquia
luke.leber
neslee canil pinto organization(s): Ramsalt Lab
greg.1.anderson organization(s): Pantheon
kristen pol organization(s): Itty Bitty Byte
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.