Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
lendude volunteering organization(s): iO
mglaman organization(s): Bluehorn Digital customer(s): Tag1 Consulting, Inc.
vakulrai volunteering organization(s): QED42 customer(s): QED42
manojbisht_drupal volunteering organization(s): Portage CyberTech customer(s): Portage CyberTech
ranjith_kumar_k_u organization(s): Zyxware Technologies
mrinalini9 organization(s): Material customer(s): Drupal India Association
kalpaitch volunteering
le72
hudri organization(s): webtourismus.at
sakthi_dev organization(s): Specbee customer(s): Drupal India Association
sea2709 volunteering organization(s): Portland Webworks
dcam volunteering
abhijith s volunteering organization(s): Zyxware Technologies
rinku jacob 13 organization(s): Zyxware Technologies
jcrump@tulane.edu
oheller
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.