Contribution records
Contributors

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

Give credit to everyone
johnnybgoode johnnybgoode
johnpitcairn johnpitcairn
dhalbert dhalbert volunteering
UmarSharif drupal007
homersheineken2 homersheineken2 volunteering
jeffglenn jeffglenn
rivimey rivimey volunteering
hartsak hartsak
vj Vj
damienmckenna damienmckenna organization(s): Current
mattgross mattgross volunteering
joshf joshf organization(s): Third and Grove
tanay.naik7 tanay.naik7 volunteering organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
dhrjgpt2005@gmail.com dhrjgpt2005 organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
Greg Varga gergely-varga
chris matthews ChrisMatthews volunteering
andrew answer AndrewAnswer volunteering
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.