Contribution records
Contributors

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

Give credit to everyone
phenaproxima phenaproxima organization(s): Acquia
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
xjm xjm organization(s): Acquia
quietone quietone volunteering organization(s): Acro Commerce
maxocub maxocub volunteering
jofitz jofitz organization(s): ComputerMinds
badmetevils badmetevils organization(s): OpenSense Labs
alexpott alexpott organization(s): Acro Commerce
catch catch organization(s): Third and Grove
mikeryan mikeryan volunteering organization(s): Virtuoso Performance
mondrake mondrake volunteering
neclimdul neclimdul
webflo webflo organization(s): UEBERBIT GmbH
mnshantz mnshantz
oknate oknate volunteering
vermario vermario
dave reid davereid volunteering organization(s): Lullabot
gábor hojtsy goba organization(s): Acquia
Chris Gillis ChrisGillis
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.