You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 lines
588 B
32 lines
588 B
3 weeks ago
|
# Proposal: 编码规范制定与实施
|
||
|
|
|
||
|
|
## Why
|
||
|
|
现有代码缺乏统一规范：
|
||
|
|
1. 代码风格不一致
|
||
|
|
2. 命名不规范
|
||
|
|
3. 注释缺失
|
||
|
|
4. 缺乏 Git 提交规范
|
||
|
|
5. 代码质量参差不齐
|
||
|
|
|
||
|
|
## What
|
||
|
|
制定并实施编码规范：
|
||
|
|
1. Java 编码规范
|
||
|
|
2. 前端编码规范
|
||
|
|
3. Git 提交规范
|
||
|
|
4. Code Review 流程
|
||
|
|
5. 自动化检查工具
|
||
|
|
|
||
|
|
## Success Criteria
|
||
|
|
1. 编码规范文档完整
|
||
|
|
2. 代码检查工具集成
|
||
|
|
3. CI/CD 自动化检查
|
||
|
|
4. 团队 100% 遵循规范
|
||
|
|
5. 代码质量提升
|
||
|
|
|
||
|
|
## Non-Goals
|
||
|
|
- 不改变业务逻辑
|
||
|
|
- 不强制重构历史代码
|
||
|
|
|
||
|
|
## Dependencies
|
||
|
|
无
|