Issue
Contribution records
Contributors

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

Give credit to everyone
prince_kr organization(s): Zyxware Technologies
naveenvalecha volunteering
elachlan
yogeshmpawar volunteering organization(s): QED42
damienmckenna organization(s): Current
urvashi_vora organization(s): Valuebound customer(s): Valuebound
jatingupta40 organization(s): QED42 customer(s): Drupal India Association
sharayurajput organization(s): QED42 customer(s): Drupal India Association
anybody organization(s): DROWL.de
amanshukla6158 organization(s): OpenSense Labs customer(s): DrupalFit
amit.drupal volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
Andreas Hansson organization(s): Axis Communications AB
ravi.shankar organization(s): OpenSense Labs
japerry organization(s): Acquia
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.