diff --git a/.gitee/ISSUE_TEMPLATE/.keep b/.gitcode/ISSUE_TEMPLATE/.keep
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/.keep
rename to .gitcode/ISSUE_TEMPLATE/.keep
diff --git a/.gitee/ISSUE_TEMPLATE/001-bug-report.yml b/.gitcode/ISSUE_TEMPLATE/001-bug-report.yml
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/001-bug-report.yml
rename to .gitcode/ISSUE_TEMPLATE/001-bug-report.yml
diff --git a/.gitee/ISSUE_TEMPLATE/002-documentation.yml b/.gitcode/ISSUE_TEMPLATE/002-documentation.yml
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/002-documentation.yml
rename to .gitcode/ISSUE_TEMPLATE/002-documentation.yml
diff --git a/.gitee/ISSUE_TEMPLATE/003-feature-request.yml b/.gitcode/ISSUE_TEMPLATE/003-feature-request.yml
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/003-feature-request.yml
rename to .gitcode/ISSUE_TEMPLATE/003-feature-request.yml
diff --git a/.gitee/ISSUE_TEMPLATE/005-blank.yml b/.gitcode/ISSUE_TEMPLATE/004-blank.yml
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/005-blank.yml
rename to .gitcode/ISSUE_TEMPLATE/004-blank.yml
diff --git a/.gitee/ISSUE_TEMPLATE/config.yml b/.gitcode/ISSUE_TEMPLATE/config.yml
similarity index 100%
rename from .gitee/ISSUE_TEMPLATE/config.yml
rename to .gitcode/ISSUE_TEMPLATE/config.yml
diff --git a/.gitee/PULL_REQUEST_TEMPLATE.en.md b/.gitcode/PULL_REQUEST_TEMPLATE.en.md
similarity index 60%
rename from .gitee/PULL_REQUEST_TEMPLATE.en.md
rename to .gitcode/PULL_REQUEST_TEMPLATE.en.md
index d1bc4a54..74c6a644 100644
--- a/.gitee/PULL_REQUEST_TEMPLATE.en.md
+++ b/.gitcode/PULL_REQUEST_TEMPLATE.en.md
@@ -1,18 +1,9 @@
 <!--  Thanks for sending a pull request!  Here are some tips for you:
 
-1) If this is your first time, please read our contributor guidelines: https://gitee.com/mindspore/mindspore/blob/master/CONTRIBUTING.md
+1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openHiTLS/openhitls/wiki/FAQ-%E7%A4%BE%E5%8C%BA%E9%9C%80%E6%B1%82%E8%B4%A1%E7%8C%AE%E6%B5%81%E7%A8%8B.md
 
-2) If you want to contribute your code but don't know who will review and merge, please add label `mindspore-assistant` to the pull request, we will find and do it as soon as possible.
 -->
 
-**What type of PR is this?**
-<!-- 
-Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. 
-
-If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`.
--->
-/kind <label>
-
 
 **What does this PR do / why do we need it**:
 * Need to describe clearly
@@ -32,9 +23,7 @@ Fixes #
 
 **Self-checklist**:（**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**）
 
-+ - [ ] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised
 + - [ ] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded.
-+ - [ ] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR.
 + - [ ] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed.
 + - [ ] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner.
 
diff --git a/.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md b/.gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md
similarity index 53%
rename from .gitee/PULL_REQUEST_TEMPLATE.zh-CN.md
rename to .gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md
index a9bbbfa8..ae6ef385 100644
--- a/.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md
+++ b/.gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md
@@ -1,23 +1,9 @@
 <!--  Thanks for sending a pull request!  Here are some tips for you:
 
-1) If this is your first time, please read our contributor guidelines: https://gitee.com/mindspore/mindspore/blob/master/CONTRIBUTING.md
+1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openHiTLS/openhitls/wiki/FAQ-%E7%A4%BE%E5%8C%BA%E9%9C%80%E6%B1%82%E8%B4%A1%E7%8C%AE%E6%B5%81%E7%A8%8B.md
 
-2) If you want to contribute your code but don't know who will review and merge, please add label `mindspore-assistant` to the pull request, we will find and do it as soon as possible.
 -->
 
-**What type of PR is this?**
-<!-- 
-选择下面一种标签替换下方 `/kind <label>`，可选标签类型有：
-- /kind bug 
-- /kind task
-- /kind feature
-- /kind refactor
-- /kind clean_code
-如PR描述不符合规范，修改PR描述后需要/check-pr重新检查PR规范。
--->
-/kind <label>
-
----
 
 **What does this PR do / why do we need it**:
 
@@ -36,11 +22,9 @@ Fixes #
 
 ---
 
-**Self-checklist**:（**请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入**）
+**Self-checklist**:（**请自检，在[ ]内打上x**）
 
-+ - [ ] **设计**：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改
 + - [ ] **测试**：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库
-+ - [ ] **验证**：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述
 + - [ ] **接口**：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确
 + - [ ] **文档**：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓
 
diff --git a/.gitee/ISSUE_TEMPLATE/004-security_report.yml b/.gitee/ISSUE_TEMPLATE/004-security_report.yml
deleted file mode 100644
index 0ce9e861..00000000
--- a/.gitee/ISSUE_TEMPLATE/004-security_report.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-name: ⚡Report a security vulnerability
-labels: ["security"]
-body:
-  - type: textarea
-    attributes:
-      label: 漏洞信息
-      description: |
-        Please clearly describe the vulnerability number, component, and version number, and clearly describe the main background and content of the vulnerability. Also note the time of disclosure, creation, and reference link for vulnerability details and analysis link.
-      placeholder: "Vulnerability information."
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: 漏洞分析结构反馈
-      description: |
-        Provide a thorough analysis of the vulnerability's impact, including vulnerability scoring for the MindSpore.
-      placeholder: "Vulnerability analysis."
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: 版本信息
-      description: 如果涉及多个版本，请悉数告知我们对应的版本号信息，以方便我们复现问题
-    validations:
-      required: true
-  - type: markdown
-    attributes:
-      value: >
-        Thanks for contributing 🎉!
\ No newline at end of file
diff --git a/.gitee/PULL_REQUEST_TEMPLATE.md b/.gitee/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index c62f68d2..00000000
--- a/.gitee/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,38 +0,0 @@
-<!--  Thanks for sending a pull request!  Here are some tips for you:
-
-1) If this is your first time, please read our contributor guidelines: https://gitee.com/mindspore/mindspore/blob/master/CONTRIBUTING.md
-
-2) If you want to contribute your code but don't know who will review and merge, please add label `mindspore-assistant` to the pull request, we will find and do it as soon as possible.
--->
-
-**What type of PR is this?**
-<!-- 
-Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. 
-
-If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`.
--->
-/kind <label>
-
-
-**What does this PR do / why do we need it**:
-
-
-**Which issue(s) this PR fixes**:
-<!-- 
-*Automatically closes linked issue when PR is merged.
-Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
--->
-Fixes #
-
-
-**Code review checklist [[illustration]](https://gitee.com/mindspore/community/blob/master/security/code_review_checklist_mechanism.md)**:
-
-+ - [ ] whether to verify the function's return value (It is forbidden to use void to mask the return values of security functions and self-developed functions. C++ STL functions can be masked if there is no problem)
-+ - [ ] Whether to comply with ***SOLID principle / Demeter's law***
-+ - [ ] Whether there is UT test case && the test case is a valid (if there is no test case, please explain the reason)
-+ - [ ] Whether the API change is involved
-+ - [ ] Whether official document modification is involved
-
-<!-- **Special notes for your reviewers**: -->
-<!-- + - [ ] Whether it causes forward compatibility failure -->
-<!-- + - [ ] Whether the dependent third-party library change is involved -->