合并受阻
感谢提交 Pull Requests ！此PR未通过DCO校验。
校验失败可能原因：
1. 未签署“DCO协议”（开发者原创声明协议），在线签署、查看签署状态。
2. Commits 中未包含 Signed-off-by信息，参考FAQ处理。
修复上述问题后，在PR的评论框输入“check dco” ，单击”评论”，系统将再次进行DCO校验。
当前检测到如下Commits 未包含Signed-off-by信息：
Thanks for submitting a pull request. This pull request has not passed the DCO check.
Possible causes:
1. You have not signed the Developer Certificate of Origin (DCO). Sign the DCO and check DCO status.
2. The commits do not contain the Signed-off-by information. To resolve this issue, see FAQs.
After resolving the preceding issues, enter check dco in the comment box of this pull request and click Comment. The system will check DCO status again.
The following commits do not contain the Signed-off-by information:
感谢提交 Pull Requests ！此PR未通过DCO校验。
校验失败可能原因：
1. 未签署“DCO协议”（开发者原创声明协议），在线签署、查看签署状态。
2. Commits 中未包含 Signed-off-by信息，参考FAQ处理。
修复上述问题后，在PR的评论框输入“check dco” ，单击”评论”，系统将再次进行DCO校验。
当前检测到如下Commits 未包含Signed-off-by信息：
Thanks for submitting a pull request. This pull request has not passed the DCO check.
Possible causes:
1. You have not signed the Developer Certificate of Origin (DCO). Sign the DCO and check DCO status.
2. The commits do not contain the Signed-off-by information. To resolve this issue, see FAQs.
After resolving the preceding issues, enter check dco in the comment box of this pull request and click Comment. The system will check DCO status again.
The following commits do not contain the Signed-off-by information:
check dco
感谢提交 Pull Requests ！此PR未通过DCO校验。
校验失败可能原因：
1. 未签署“DCO协议”（开发者原创声明协议），在线签署、查看签署状态。
2. Commits 中未包含 Signed-off-by信息，参考FAQ处理。
修复上述问题后，在PR的评论框输入“check dco” ，单击”评论”，系统将再次进行DCO校验。
当前检测到如下Commits 未包含Signed-off-by信息：
Thanks for submitting a pull request. This pull request has not passed the DCO check.
Possible causes:
1. You have not signed the Developer Certificate of Origin (DCO). Sign the DCO and check DCO status.
2. The commits do not contain the Signed-off-by information. To resolve this issue, see FAQs.
After resolving the preceding issues, enter check dco in the comment box of this pull request and click Comment. The system will check DCO status again.
The following commits do not contain the Signed-off-by information:
感谢提交 Pull Requests ！此PR未通过DCO校验。
校验失败可能原因：
1. 未签署“DCO协议”（开发者原创声明协议），在线签署、查看签署状态。
2. Commits 中未包含 Signed-off-by信息，参考FAQ处理。
修复上述问题后，在PR的评论框输入“check dco” ，单击”评论”，系统将再次进行DCO校验。
当前检测到如下Commits 未包含Signed-off-by信息：
Thanks for submitting a pull request. This pull request has not passed the DCO check.
Possible causes:
1. You have not signed the Developer Certificate of Origin (DCO). Sign the DCO and check DCO status.
2. The commits do not contain the Signed-off-by information. To resolve this issue, see FAQs.
After resolving the preceding issues, enter check dco in the comment box of this pull request and click Comment. The system will check DCO status again.
The following commits do not contain the Signed-off-by information:
感谢提交 Pull Requests ！此PR未通过DCO校验。
校验失败可能原因：
1. 未签署“DCO协议”（开发者原创声明协议），在线签署、查看签署状态。
2. Commits 中未包含 Signed-off-by信息，参考FAQ处理。
修复上述问题后，在PR的评论框输入“check dco” ，单击”评论”，系统将再次进行DCO校验。
当前检测到如下Commits 未包含Signed-off-by信息：
Thanks for submitting a pull request. This pull request has not passed the DCO check.
Possible causes:
1. You have not signed the Developer Certificate of Origin (DCO). Sign the DCO and check DCO status.
2. The commits do not contain the Signed-off-by information. To resolve this issue, see FAQs.
After resolving the preceding issues, enter check dco in the comment box of this pull request and click Comment. The system will check DCO status again.
The following commits do not contain the Signed-off-by information:
感谢提交 Pull Requests！如果您提交的PR已经开发完毕，请评论 "start build" 触发门禁，更多交互操作，请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态，请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.
感谢提交 Pull Requests！如果您提交的PR已经开发完毕，请评论 "start build" 触发门禁，更多交互操作，请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态，请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.
感谢提交 Pull Requests！如果您提交的PR已经开发完毕，请评论 "start build" 触发门禁，更多交互操作，请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态，请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.
感谢提交 Pull Requests！如果您提交的PR已经开发完毕，请评论 "start build" 触发门禁，更多交互操作，请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态，请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.
一、内容说明（相关的Issue）
二、建议测试周期和提测地址
建议测试完成时间：xxxx.xx.xx
投产上线时间：xxxx.xx.xx
提测地址：CI环境/压测环境
测试账号：
三、变更内容
3.1 关联PR列表
3.2 数据库和部署说明
bundle exec xxx RAILS_ENV = production；没有写 "无"3.4 其他技术优化内容（做了什么，变更了什么）
3.5 废弃通知（什么字段、方法弃用？）
3.6 后向不兼容变更（是否有无法向后兼容的变更？）
四、研发自测点（自测哪些？冒烟用例全部自测？）
自测测试结论：
五、测试关注点（需要提醒QA重点关注的、可能会忽略的地方）
检查点：
接口测试：
性能测试：
并发测试：
其他：