Issue
Contribution records
Contributors

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

Give credit to everyone
mtift organization(s): Lullabot
thejimbirch organization(s): Kanopi Studios
hansa11 organization(s): Ramsalt Lab
kunal_kapoor volunteering organization(s): OpenSense Labs
starshaped organization(s): Lullabot
markdorison organization(s): Chromatic
anjalivijay organization(s): Axelerant
scorbine organization(s): Bounteous
mansoor20 volunteering
gauravvvv organization(s): OpenSense Labs
volkswagenchick organization(s): Kanopi Studios
shaal volunteering organization(s): Phase2
brianperry organization(s): Bounteous
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
mherchel organization(s): Lullabot
andy-blum organization(s): Lullabot
sakthivel m organization(s): QED42 customer(s): Drupal India Association
neslee canil pinto organization(s): Ramsalt Lab
rahul b organization(s): Zyxware Technologies
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.