Contribution records
Draft
Contributors

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

Give credit to everyone
stockfoot Stockfoot organization(s): Kanopi Studios
bspeare bspeare
gauravvvv Gauravmahlawat organization(s): Axelerant customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
nod_ nod_ organization(s): Eclipse Foundation, Très Bien Tech
sourabhjain sourabh_jain_419 organization(s): Valuebound customer(s): Valuebound
santosh_verma Santosh_Verma organization(s): Material customer(s): Drupal India Association
_pratik_ k_pratik volunteering organization(s): Specbee customer(s): Drupal India Association
meeni_dhobale meeni_dhobale volunteering organization(s): QED42
psebborn psebborn organization(s): Zoocha
sandeepmahlawat SandeepMahlawat organization(s): Innoraft
sourojeetpaul sourojeet2001 volunteering organization(s): Innoraft customer(s): Drupal India Association
nayana_mvr Nayana_R organization(s): Material
stanzin Stanzin7 volunteering
andol andol
shweta__sharma shwetaoti organization(s): OpenSense Labs
mithun s Mithun_S customer(s): QED42
sanket.tale stale organization(s): QED42
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.