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
quietone quietone volunteering organization(s): Acro Commerce
neclimdul neclimdul organization(s): APQC
andypost andypost volunteering organization(s): Skilld
mondrake mondrake volunteering
mikelutz mdlutz volunteering organization(s): Four Kitchens
catch catch organization(s): Third and Grove
benjifisher benjifisher volunteering organization(s): FRUITION
xurizaemon xurizaemon volunteering organization(s): Catalyst IT
smustgrave smustgrave organization(s): Mobomo
jofitz jofitz organization(s): jofitz
godotislate godotislate volunteering
wim leers wimleers organization(s): Acquia
moshe weitzman weitzman
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.