Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
saschaeggi organization(s): Unic
lauriii organization(s): Acquia
huzooka organization(s): Cheppers customer(s): Acquia
asmita26 volunteering organization(s): QED42
hansa11 volunteering organization(s): QED42
indrajithkb organization(s): Material customer(s): Drupal India Association
deepalij organization(s): QED42 customer(s): Drupal India Association
komalk organization(s): Material customer(s): Drupal India Association
KondratievaS organization(s): Skilld
ranjith_kumar_k_u organization(s): Zyxware Technologies
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
ckrina organization(s): Lullabot
volkswagenchick organization(s): Kanopi Studios
gauravvvv organization(s): Axelerant, OpenSense Labs customer(s): Drupal India Association
marcusvsouza organization(s): CI&T
laisbonafe organization(s): CI&T
kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
sakthivel m organization(s): QED42 customer(s): Drupal India Association
divya.sejekan organization(s): QED42 customer(s): Drupal India Association
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.