Contribution records
Contributors

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

Give credit to everyone
mxh hauptm volunteering organization(s): OpenCampus GmbH
avpaderno avpaderno volunteering
chaitanyadessai chaitanyadessai organization(s): Specbee
sidharth_soman sidharth_soman organization(s): Valuebound customer(s): Valuebound
mrinalini9 mrinalini9 organization(s): Material customer(s): Drupal India Association
shiv_sharma Shiv_Sharma organization(s): Melity
nitin_lama nitin_lama organization(s): Specbee
atul_ghate atulghate organization(s): Innoraft customer(s): Drupal India Association
samitk samit.310 organization(s): Material customer(s): Drupal India Association
charchil khandelwal Charchil_Khandelwal organization(s): Dotsquares Ltd.
nikolay shapovalov zniki.ru volunteering
a.aaronjake a.aaronjake volunteering organization(s): Promet Source
mandclu mandclu volunteering organization(s): Acquia
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.