docs: add requirement for English PR descriptions in development workflow

This commit is contained in:
overtrue
2025-05-25 13:55:51 +08:00
parent bc398ccf1b
commit ad71db6367

View File

@@ -366,3 +366,9 @@ These rules should serve as guiding principles when developing the RustFS projec
- After each development completion, first git push to remote repository
- After each change completion, summarize the changes, do not create summary files, provide a brief change description, ensure compliance with [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
- Provide change descriptions needed for PR in the conversation, ensure compliance with [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
- **Always provide PR descriptions in English** after completing any changes, including:
- Clear and concise title following Conventional Commits format
- Detailed description of what was changed and why
- List of key changes and improvements
- Any breaking changes or migration notes if applicable
- Testing information and verification steps