Lines Matching +full:project +full:- +full:model

5 <!-- TOC -->
7 - [MindSpore contributing guidelines](#mindspore-contributing-guidelines)
8     - [Contributor License Agreement](#contributor-license-agreement)
9     - [Getting Started](#getting-started)
10     - [Contribution workflow](#contribution-workflow)
11         - [Code style](#code-style)
12         - [Fork-Pull development model](#fork-pull-development-model)
13         - [Report issues](#report-issues)
14         - [Propose PRs](#propose-prs)
16 <!-- /TOC -->
26 - Fork the repository on [Github](https://github.com/mindspore-ai/mindspore) or [Gitee](https://git…
27 - Read the [README.md](README.md) and [install page](https://www.mindspore.cn/install/en) for proje…
35 - Coding guidelines
37 ….net), [CMakeLint](https://github.com/cmake-lint/cmake-lint), [CodeSpell](https://github.com/codes…
39 - Unittest guidelines
43 - Refactoring guidelines
47 - Document guidelines
50 …- MD007 (unordered list indentation): The **indent** parameter is set to **4**, indicating that al…
51 …- MD009 (spaces at the line end): The **br_spaces** parameter is set to **2**, indicating that the…
52 …- MD029 (sequence numbers of an ordered list): The **style** parameter is set to **ordered**, indi…
56 ### Fork-Pull development model
58 - Fork MindSpore repository
60 …Before submitting code to MindSpore project, please make sure that this project have been forked t…
62 - Clone the remote repository
69     git remote add upstream https://github.com/mindspore-ai/mindspore.git
75 - Develop code locally
80     git checkout -b {new_branch_name} origin/master
86 - Push the code to the remote repository
93     git commit -m "Your commit title"
94     git commit -s --amend #Add the concrete description of your commit
98 - Pull a request to MindSpore repository
104 …eat way to contribute to the project is to send a detailed report when you encounter an issue. We …
108 - What version of env (mindspore, os, python etc) are you using?
109 - Is this a BUG REPORT or FEATURE REQUEST?
110 - What kind of issue is, add the labels to highlight it on the issue dashboard.
111 - What happened?
112 - What you expected to happen?
113 - How to reproduce it?(as minimally and precisely as possible)
114 - Special notes for your reviewers?
118 - **If you find an unclosed issue, which is exactly what you are going to solve,** please put some …
119 - **If an issue is opened for a while,** it's recommended for contributors to precheck before worki…
120 - **If you resolve an issue which is reported by yourself,** it's also required to let others know …
121 - **If you want the issue to be responded as quickly as possible,** please try to label it, you can…
125 - Raise your idea as an *issue* on [GitHub](https://github.com/mindspore-ai/mindspore/issues) or [G…
126 - If it is a new feature that needs lots of design details, a design proposal should also be submit…
127 - After reaching consensus in the issue discussions and design proposal reviews, complete the devel…
128 - None of PRs is not permitted until it receives **2+ LGTM** from approvers. Please NOTICE that app…
129 - After PR is sufficiently discussed, it will get merged, abandoned or rejected depending on the ou…
133 - Any irrelevant changes should be avoided.
134 - Make sure your commit history being ordered.
135 - Always keep your branch up with the master branch.
136 - For bug-fix PRs, make sure all related issues being linked.