Contribution records
Contributors

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

Give credit to everyone
sergiuteaca sergiuteaca organization(s): JAKALA (formerly FFW)
shailja179 shailja179 organization(s): Material customer(s): Drupal India Association
phenaproxima phenaproxima organization(s): Acquia
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
naresh_bavaskar naresh3419 volunteering organization(s): QED42 customer(s): Drupal India Association
janmejaig janmejaig organization(s): Material customer(s): Drupal India Association
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
tanubansal tanubansal organization(s): Salsa Digital
alexpott alexpott organization(s): Acro Commerce, Thunder
xjm xjm organization(s): Acquia
cilefen cilefen
ramya balasubramanian RamyaBalasubramanian organization(s): Material customer(s): Drupal India Association
pranali.lanjewar pranali.lanjewar
Vidushi Mehta VidushiMehta organization(s): gai Technologies Pvt Ltd
chr.fritsch chr.fritsch organization(s): Thunder
Christopher Riley cmriley
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.