Contribution records
Draft
Contributors

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

Give credit to everyone
mxh hauptm volunteering organization(s): OpenCampus GmbH
juancec juancec organization(s): CI&T
atul_ghate atulghate volunteering organization(s): QED42
nitin_lama nitin_lama organization(s): Specbee
vishaljd vishaljd organization(s): Valuebound
avpaderno avpaderno volunteering
elber elber organization(s): CI&T
indrapatil indra organization(s): Valuebound customer(s): Valuebound
mahima_mathur23 Mahima_Mathur23 organization(s): Material customer(s): Drupal India Association
nisha_j nisha_j
sakthi_dev sakthi_dev organization(s): Specbee customer(s): Drupal India Association
pray_12 Preethy_ray organization(s): Specbee
Harsh panchal Harshpanchal organization(s): Smashing Infolabs Pvt. Ltd. customer(s): Smashing Infolabs Pvt. Ltd.
dharti patel Dhariyank volunteering organization(s): QED42
Shreyas gowda Shreyas_k
bindu r bindu_r
zkhan.aamir zkhan.aamir organization(s): Specbee customer(s): Drupal India Association
silvi.addweb silvi.addweb organization(s): AddWeb Solution Pvt. Ltd. customer(s): AddWeb Solution Pvt. Ltd.
aurora.luzzardi aluzzardi
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.