Issue
Contribution records
Contributors

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

Give credit to everyone
penyaskito organization(s): Lingotek
tushar_sachdeva organization(s): OpenSense Labs
mherchel organization(s): Lullabot
sulfikar_s organization(s): Zyxware Technologies
pragati_kanade organization(s): QED42 customer(s): Drupal India Association
renatog organization(s): CI&T
kostyashupenko organization(s): Skilld
guilhermevp organization(s): CI&T
ajv009 volunteering organization(s): QED42 customer(s): Drupal India Association
marcusvsouza organization(s): CI&T
indrajithkb organization(s): Material customer(s): Drupal India Association
lauriii organization(s): Acquia
kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
sakthivel m organization(s): QED42 customer(s): Drupal India Association
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.