| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Sync PyPTO Pro API annotations and docs Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !6873 merge docs-pro-sync-0902 into master Sync PyPTO Pro API annotations and docs Created-by: gcw_bTlukKC6 Commit-by: gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 fix 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 Related Issue: 放到描述信息最后。 下面是一个典型的PR描述信息: The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!6873 | 19 小时前 | |
fix(docs): Updata the doc menu title. Co-authored-by: lyz0328<liyanzhen@huawei.com> # message auto-generated for no-merge-commit merge: !5992 merge master into master fix(docs): Updata the doc menu title. Created-by: lyz0328 Commit-by: lyz0328 Merged-by: cann-robot Description: 更新文档目录标题、新增昇腾社区文档目录文件index_hiascend.md See merge request: cann/pypto!5992 | 1 个月前 | |
feat(docs): Modify the product name Co-authored-by: lyz0328<liyanzhen@huawei.com> # message auto-generated for no-merge-commit merge: !6558 merge master into master feat(docs): Modify the product name Created-by: lyz0328 Commit-by: lyz0328 Merged-by: cann-robot Description: 统一修改产品型号： Ascend 950PR/Ascend 950DT > Ascend 950PR&950DT系列产品 Atlas A3 训练系列产品/Atlas A3 推理系列产品 > Atlas A3系列产品 Atlas A2 训练系列产品/Atlas A2 推理系列产品 > Atlas A2系列产品 See merge request: cann/pypto!6558 | 24 天前 | |
docs: fix documentation errors Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !6727 merge docs-pro-sync-0902 into master docs: fix documentation errors Created-by: gcw_bTlukKC6 Commit-by: gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 fix 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 Related Issue: 放到描述信息最后。 下面是一个典型的PR描述信息: The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!6727 | 15 天前 | |
feat(docs): Modify the product name Co-authored-by: lyz0328<liyanzhen@huawei.com> # message auto-generated for no-merge-commit merge: !6558 merge master into master feat(docs): Modify the product name Created-by: lyz0328 Commit-by: lyz0328 Merged-by: cann-robot Description: 统一修改产品型号： Ascend 950PR/Ascend 950DT > Ascend 950PR&950DT系列产品 Atlas A3 训练系列产品/Atlas A3 推理系列产品 > Atlas A3系列产品 Atlas A2 训练系列产品/Atlas A2 推理系列产品 > Atlas A2系列产品 See merge request: cann/pypto!6558 | 24 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 19 小时前 | ||
| 1 个月前 | ||
| 24 天前 | ||
| 15 天前 | ||
| 24 天前 |