Issue
Contribution records
Contributors

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

Give credit to everyone
phenaproxima organization(s): Acquia
benjy organization(s): PreviousNext
quietone volunteering
mikeryan volunteering organization(s): Virtuoso Performance
heddn organization(s): Acro Commerce, MTech, LLC
imiksu volunteering
jofitz organization(s): ComputerMinds
robpowell volunteering
alexpott organization(s): Acro Commerce, Thunder
yogeshmpawar organization(s): QED42
catch organization(s): Third and Grove
neclimdul organization(s): APQC
berdir organization(s): MD Systems GmbH
wim leers organization(s): Acquia
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.