Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
drumanuel
ckrina organization(s): Lullabot
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
gauravvvv organization(s): Material customer(s): Drupal India Association
hmendes organization(s): CI&T
maninders organization(s): Material
ambikahirode volunteering organization(s): Material customer(s): Drupal India Association
tinto organization(s): The Savvy Few
lauriii organization(s): Acquia
fadilraj volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
smustgrave organization(s): Mobomo
bnjmnm organization(s): Acquia
dsandhya organization(s): Melity
rpayanm organization(s): Agileana
karanpagare volunteering organization(s): QED42 customer(s): Drupal India Association
stuckinconcretejungle volunteering
ahsannazir organization(s): QED42
javi-er organization(s): Lullabot
gaurav-mathur organization(s): Dotsquares Ltd.
sonam.chaturvedi organization(s): Salsa Digital
saurav-drupal-dev volunteering organization(s): Material customer(s): Drupal India Association
quietone organization(s): PreviousNext
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.