Contribution records
Contributors

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

Give credit to everyone
megachriz megachriz volunteering organization(s): WebCoo
toki Toki
gkaas gkaas volunteering
liquidcms liquidcms
drupaldope drupaldope
nattyweb NattyWebDev
fristaila fristaila volunteering
mitchems mitchems
andileco andileco organization(s): JSI Research & Training Institute, Inc. (JSI)
ptmkenny ptmkenny
yang_yi_cn yangyicn organization(s): Yi Commerce Solutions
blogchef12 blogchef12
tsurvuli tsurvuli
socialnicheguru SocialNicheGuru
rpayanm rpayanm organization(s): weKnow Inc customer(s): Kanopi Studios
saranya ashokkumar saranyapurushothaman organization(s): UniMity Solutions Pvt Limited
vrajak@gmail.com Vraja
sriharsha.uppuluri sriharsha.uppuluri organization(s): QED42
niki v niki_v
rohit.rawat619 RohitRawat676 organization(s): TO THE NEW
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.