mirror of
https://github.com/rustfs/rustfs.git
synced 2026-09-05 19:55:37 +00:00
Zhengchao An
37 lines
1.7 KiB
Markdown
37 lines
1.7 KiB
Markdown
<!--
|
||
Pull Request Template for RustFS
|
||
-->
|
||
|
||
## Related Issues
|
||
<!--
|
||
List related issues, e.g. Fixes #123.
|
||
Use N/A when there is no related issue.
|
||
-->
|
||
|
||
## Summary of Changes
|
||
<!--
|
||
Describe the concrete problem and resulting behavior. For a behavior change, name the input or state that triggers it and the expected outcome. Explain any new dependency or abstraction that the change needs.
|
||
-->
|
||
|
||
## Verification
|
||
<!--
|
||
Give 1–3 concrete pieces of evidence for the changed behavior: the test or command, its observed result, and the regression it catches. For a bug fix, record a failing-before/passing-after check or explain why it was unavailable.
|
||
|
||
Identify the tested commit and any local changes. When testing a prebuilt binary or external service, include its source/version and artifact identity; a successful run against a different build is not evidence for this change.
|
||
|
||
List relevant checks not run and the remaining risk. Use the validation tier in AGENTS.md; do not run broader checks solely to fill this section. For documentation-only changes, list the applicable documentation checks. Use N/A only when verification is not applicable.
|
||
-->
|
||
|
||
## Impact
|
||
<!--
|
||
Describe user-facing, compatibility, API, deployment, configuration, or
|
||
documentation impact. Use N/A when there is no expected impact.
|
||
-->
|
||
|
||
## Additional Notes
|
||
<!-- Any extra information for reviewers, or N/A. -->
|
||
|
||
---
|
||
|
||
Thank you for your contribution! Please ensure your PR follows the community standards ([CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)). If this is your first contribution, review the [CLA document](https://github.com/rustfs/cla/blob/main/cla/v2.md) and sign it by commenting `I have read and agree to the CLA.` on the PR.
|