Issue
Contribution records
Contributors

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

Give credit to everyone
naveenvalecha volunteering
sreenivasparuchuri volunteering
berdir organization(s): MD Systems GmbH
WidgetsBurritos organization(s): Rackspace
ankush_03 organization(s): Material customer(s): Drupal India Association
rksyravi volunteering organization(s): Material customer(s): Drupal India Association
akashkumar07 organization(s): OpenSense Labs
andreyjan organization(s): JAKALA (formerly FFW)
lestat organization(s): EPAM
jeroent organization(s): iO
swatichouhan012 organization(s): Valuebound customer(s): Valuebound
wundo organization(s): Chuva Inc.
gambry organization(s): manifesto
heddn organization(s): MTech, LLC
adrianpintilie organization(s): Softescu
japerry organization(s): Acquia
iyyappan.govind volunteering organization(s): BORN Commerce, UniMity Solutions Pvt Limited customer(s): Drupal India Association
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
lisa.rae volunteering organization(s): Interpersonal Frequency
neslee canil pinto organization(s): Specbee
kim.pepper
gaëlg organization(s): Insite
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.