Issue
Contribution records
Contributors

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

Give credit to everyone
rishu_kumar organization(s): QED42
tr
rahul17 organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
driskell volunteering organization(s): Other Media
salvis volunteering organization(s): Salvisberg Software & Consulting
shivam_tiwari organization(s): Atlas Softweb Pvt Ltd, Innoraft
ruscoe volunteering
sundhar volunteering organization(s): Drupal Developers Studio
colan organization(s): Consensus Enterprises
chadmandoo
joseph.olstad
la vague illuminee volunteering
rohan-sinha organization(s): Material
maris.abols
hemangi.gokhale volunteering organization(s): Redfin Solutions, LLC
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.