Contribution records
Contributors

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

Give credit to everyone
capellic capellic
phenaproxima phenaproxima organization(s): Acquia
rdeboer rdeboer
bleen bleen18 organization(s): NBCUniversal
chandu7929 chandu7929
matthiasm11 matthiasm11 organization(s): MM-Experience
bygeoffthompson bygeoffthompson
thejimbirch thejimbirch organization(s): Kanopi Studios
damontgomery damontgomery organization(s): Phase2
wil2091 wilfred-arambhan volunteering organization(s): Moonraft Innovation Labs
devkinetic devkinetic
siramsay siramsay volunteering
dwisnousky daniellew volunteering
dasginganinja dasginganinja organization(s): Lehigh University
rajeshreeputra Rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc. customer(s): Shivswarajya Inc.
damienmckenna damienmckenna volunteering
abh.ai abh.ai volunteering organization(s): QED42
man-1982 man-1982 volunteering
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.