Issue
Contribution records
Contributors

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

Give credit to everyone
mayurjadhav organization(s): Material
msuthars organization(s): QED42 customer(s): Drupal India Association
phenaproxima organization(s): Acquia
dww volunteering organization(s): TEN7
alexpott organization(s): Acro Commerce, Thunder
vsujeetkumar organization(s): Material customer(s): Drupal India Association
kishor_kolekar volunteering organization(s): QED42 customer(s): Drupal India Association
vakulrai volunteering organization(s): gai Technologies Pvt Ltd, QED42 customer(s): gai Technologies Pvt Ltd, QED42
quietone volunteering
sanjayk volunteering organization(s): Material customer(s): Drupal India Association
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
jonathan1055 volunteering
dave reid volunteering
kristen pol organization(s): Hook 42
ravi.shankar organization(s): OpenSense Labs
wim leers organization(s): Acquia
scottsawyer volunteering
kim.pepper organization(s): PreviousNext
mohit_aghera 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.