Issue
Contribution records
Contributors

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

Give credit to everyone
sivaji_ganesh_jojodae volunteering
sonvir249 volunteering
hardik_patel_12 organization(s): QED42 customer(s): Drupal India Association
alexpott organization(s): Acro Commerce, Thunder
aaronmchale
benjifisher organization(s): FRUITION, Hook 42
tedbow organization(s): Acquia
worldlinemine organization(s): Acquia
webchick organization(s): Acquia
tanubansal organization(s): Salsa Digital
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
ranjith_kumar_k_u organization(s): Zyxware Technologies
djsagar organization(s): OpenSense Labs
vikashsoni volunteering organization(s): Zyxware Technologies
hmendes organization(s): CI&T
gábor hojtsy organization(s): Acquia
abhijith s volunteering organization(s): Zyxware Technologies
rinku jacob 13 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.