Issue
Contribution records
Contributors

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

Give credit to everyone
vonreyes
Revshaddy
crawleyhost volunteering organization(s): Bright Plum, Inc. customer(s): Drupal Association
gbeezus volunteering
jeremycaldwell volunteering
jwmarker
kathc volunteering
myfriend2me volunteering
barbarae
chrisodva organization(s): FRUITION
feilauren volunteering
jkriigel
lauriii organization(s): Acquia
leslieg organization(s): Redfin Solutions, LLC
sundarcreosen
mserven
b_cox
cellear volunteering
crasx volunteering organization(s): Bounteous
dougvann organization(s): SynapticBlue Inc
gonz volunteering
highermath volunteering organization(s): Cherry Hill Company
isiteit volunteering
kbell organization(s): Gotham City Drupal, LLC customer(s): Find Know Do
robertrand
willtech
jlconnor
kuldeep_mehra27 organization(s): Valuebound customer(s): Valuebound
ijf8090 volunteering
Rain-Hendrix
gábor hojtsy organization(s): Acquia
darren oh organization(s): Cognizant Softvision customer(s): Estée Lauder Companies
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.