Issue
Contribution records
Contributors

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

Give credit to everyone
juampynr organization(s): Lullabot
tedbow organization(s): Acquia
marthinal
Grayside organization(s): Phase2 customer(s): Norwegian Cruise Line
rogierbom volunteering organization(s): Synetic
JamesK organization(s): Advisor Websites
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
rpayanm organization(s): SeeD EM
blackbull77
senpai
kaymccormick volunteering
gvso organization(s): Google Code-In
sgoelz
pasive volunteering
clemens.tolboom volunteering
rene bakx
jayelless volunteering
Arthur Chan volunteering
manu manu volunteering
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.