Issue
Contribution records
Contributors

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

Give credit to everyone
tetranz organization(s): Third and Grove
rgpublic
lendude organization(s): iO
vasike volunteering organization(s): drunomics, JAKALA (formerly FFW), NDP customer(s): drunomics, JAKALA (formerly FFW), NDP
vikashsoni volunteering organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
idebr organization(s): iO
joevagyok customer(s): European Commission and European Union Institutions, Agencies and Bodies
xjm organization(s): Salsa Digital, xjm
harlor organization(s): erdfisch customer(s): WERTGARANTIE Bike GmbH
longwave organization(s): Full Fat Things
pankaj.singh volunteering organization(s): Material customer(s): Drupal India Association
chaithanya.m organization(s): Zyxware Technologies
er.garg.karan volunteering 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.