Thank you for your valuable time. Your contributions will make this project better! Before submitting a contribution, please take some time to read the getting started guide below.
This project follows semantic versioning. We release patch versions for important bug fixes, minor versions for new features or non-important changes, and major versions for significant and incompatible changes.
Each major change will be recorded in the changelog
.
- Fork this repository and create a branch from
main
. For new feature implementations, submit a pull request to thefeature
branch. For other changes, submit to themain
branch. - Install the
pnpm
tool usingnpm install pnpm -g
. - Install the
Eslint
plugin forVSCode
, or enableeslint
functionality for other editors such asWebStorm
. - Execute
pnpm bootstrap
in the root directory. - Execute
pnpm install
in the/service/
directory. - Make changes to the codebase. If applicable, ensure that appropriate testing has been done.
- Execute
pnpm lint:fix
in the root directory to perform a code formatting check. - Execute
pnpm type-check
in the root directory to perform a type check. - Submit a git commit, following the Commit Guidelines.
- Submit a
pull request
. If there is a correspondingissue
, please link it using the linking-a-pull-request-to-an-issue keyword.
Commit messages should follow the conventional-changelog standard:
<type>[optional scope]: <description>
[optional body]
[optional footer]
The following is a list of commit types:
- feat: New feature or functionality
- fix: Bug fix
- docs: Documentation update
- style: Code style or component style update
- refactor: Code refactoring, no new features or bug fixes introduced
- perf: Performance optimization
- test: Unit test
- chore: Other commits that do not modify src or test files