- vanilla nginx + Rust 动态模块(取代 OpenResty+Lua),共享内存为运行期真源 - 三域名分流 18098 ssl:mdm 管理台 / lm LLM 代理 / *.dm 企业转发,共用 *.mayishangshu.cn 通配符证书(证书不入库) - LLM 统一出口:同 Key 鉴权、上游 Key 替换、白名单、限流配额、SSE - 回归夹具 tests/(网关 55 + LLM 34 = 89 断言,夹具 cp 覆盖重置) - 文档:readme(16 章)+ CLAUDE.md + conf/tls/README(acme.sh 证书管理、hairpin 环回链路)
56 lines
2.3 KiB
Markdown
56 lines
2.3 KiB
Markdown
# Contributing Guidelines
|
||
|
||
The following is a set of guidelines for contributing. We really appreciate that you are considering contributing!
|
||
|
||
#### Table Of Contents
|
||
|
||
[Ask a Question](#ask-a-question)
|
||
|
||
[Contributing](#contributing)
|
||
|
||
[Style Guides](#style-guides)
|
||
* [Git Style Guide](#git-style-guide)
|
||
* [Rust Style Guide](#rust-style-guide)
|
||
|
||
[Code of Conduct](CODE_OF_CONDUCT.md)
|
||
|
||
## Ask a Question
|
||
|
||
Please ask your question on github using discussions.
|
||
|
||
## Contributing
|
||
|
||
### Report a Bug
|
||
|
||
To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please ensure the issue has not already been reported.
|
||
|
||
### Suggest an Enhancement
|
||
|
||
To suggest an enhancement, please create an issue on GitHub with the label `enhancement` using the available feature issue template.
|
||
|
||
### Open a Pull Request
|
||
|
||
* Fork the repo, create a branch, submit a PR when your changes are tested and ready for review.
|
||
* Fill in [our pull request template](/.github/PULL_REQUEST_TEMPLATE.md)
|
||
|
||
Note: if you’d like to implement a new feature, please consider creating a feature request issue first to start a discussion about the feature.
|
||
|
||
## Style Guides
|
||
|
||
### Git Style Guide
|
||
|
||
* Keep a clean, concise and meaningful git commit history on your branch, rebasing locally and squashing before submitting a PR
|
||
* Use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format when writing a commit message, so that changelogs can be automatically generated
|
||
* Follow the guidelines of writing a good commit message as described [here](https://chris.beams.io/posts/git-commit/) and summarised in the next few points
|
||
* In the subject line, use the present tense ("Add feature" not "Added feature")
|
||
* In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
|
||
* Limit the subject line to 72 characters or less
|
||
* Reference issues and pull requests liberally after the subject line
|
||
* Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`)
|
||
|
||
### Rust Style Guide
|
||
|
||
* Rust code should be checked in after `cargo fmt` has been run.
|
||
* The code style broadly complies with the [official Rust Style Guide](https://doc.rust-lang.org/style-guide/index.html).
|
||
* Where feasible, include unit tests.
|