add readme, issue and pr templates

Author: xing-yiren

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,96 @@
+name: 🐞 Bug report
+description: Create a report to help us reproduce and fix the bug
+title: "[Bug] "
+labels: ['bug']
+
+body:
+- type: checkboxes
+  attributes:
+    label: Checklist
+    options:
+    - label: 1. I have searched related issues but cannot get the expected help.
+    - label: 2. The bug has not been fixed in the latest version.
+    - label: 3. I have read [Contributing Guidlines](https://github.com/xing-yiren/course_organization_template/wiki/%F0%9F%A7%AD-Contributing-Guidelines:-Issues-&-Pull-Requests).
+    - label: 4. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
+    - label: 5. If the issue you raised is not a bug but a question, please raise a discussion at [Discussions](https://github.com/xing-yiren/course_organization_template/discussions/new/choose) Otherwise, it will be closed.
+- type: textarea
+  attributes:
+    label: Describe the bug
+    description: |
+      A clear and concise description of what the bug is, including:
+        - What happened (actual behavior)
+        - What you expected (expected outcome)
+        - **Please attach error logs or screenshots if possible**—this helps us locate the issue faster.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Reproduction
+    description: |
+      What command or script did you run? Please list the exact steps to reproduce the bug.
+    placeholder: |
+      A placeholder for the command.
+  validations:
+    required: true
+- type: checkboxes
+  id: hardware
+  attributes:
+    label: Hardware Environment
+    description: Which hardware type does this bug relate to (select all that apply)?
+    options:
+      - label: Ascend
+      - label: GPU
+      - label: CPU
+  validations: 
+    required: true
+- type: input
+  attributes:
+    label: OS Platform
+    description: Which operating system are you using? (e.g., Ubuntu 20.04)
+    placeholder: "Ubuntu 20.04"
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Python Version
+    description: What version of Python are you using? (e.g., 3.9.7)
+    placeholder: "3.9.7"
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: MindSpore Version
+    description: What version of MindSpore are you using? (e.g., 2.7.1)
+    placeholder: "2.7.1"
+  validations:
+    required: true
+- type: input
+  id: mindspore_nlp
+  attributes:
+    label: (Optional) MindSpore NLP Version
+    placeholder: e.g., 0.5.0
+  validations:
+    required: false
+- type: input
+  id: mindspore_transformers
+  attributes:
+    label: (Optional) MindSpore Transformers Version
+    placeholder: e.g., 1.7.0
+  validations:
+    required: false
+- type: textarea
+  id: other_suites
+  attributes:
+    label: (Optional) Other Toolkit or Suite Versions
+    description: |
+      Specify versions of any other MindSpore-related suites (e.g., MindSpore Lite, vLLM-MindSpore) or relevant third-party packages.
+    placeholder: |
+      e.g.,
+      - MindSpore Lite 2.7.0
+      - vLLM-MindSpore 0.4.0
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Additional Context
+    description: Any other details.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,39 @@
+name: 🚀 Feature request
+description: Suggest an idea for this project
+title: "[Feature] "
+
+body:
+- type: checkboxes
+  attributes:
+    label: Checklist
+    options:
+    - label: 1. I have read [Contributing Guidlines](https://github.com/xing-yiren/course_organization_template/wiki/%F0%9F%A7%AD-Contributing-Guidelines:-Issues-&-Pull-Requests).
+    - label: 2. If the issue you raised is not a feature but a question, please raise a discussion at [Discussions](https://github.com/xing-yiren/course_organization_template/discussions/new/choose) Otherwise, it will be closed.
+- type: textarea
+  attributes:
+    label: Motivation
+    description: |
+      A clear and concise description of the motivation of the feature.
+  validations:
+    required: true
+- type: checkboxes
+  id: hardware
+  attributes:
+    label: Hardware Environment
+    description: Which hardware does this feature need to support (select all that apply)?
+    options:
+      - label: Ascend
+      - label: GPU
+      - label: CPU
+  validations:
+    required: true  
+- type: textarea
+  attributes:
+    label: Related resources
+    description: |
+      If there is an official code release or third-party implementations, please also provide the information here, which would be very helpful.
+- type: textarea
+  attributes:
+    label: Your Contribution
+    description: |
+      Is there any way that you could help, e.g., by submitting a PR?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+<!--
+Thank you for contributing to this project! 🎉
+Please make sure your pull request follows the contribution standards so the review and merge process can go smoothly.
+-->
+
+# Description
+<!--
+Briefly describe the purpose of this PR — what it does, why it’s needed, and which issue(s) it addresses.
+Use “Fixes #<issue_number>” if applicable.
+-->
+
+# Changes
+<!--
+Summarize key modifications — new features, bug fixes, refactors, or documentation updates.
+-->
+
+# Testing & Benchmark
+<!--
+If applicable, include test results (e.g., unit tests, accuracy verification, performance benchmarks).
+Please attach **logs, screenshots or reports** demonstrating that the code runs successfully and produces the expected results.
+-->
+
+# Checklist
+
+- [ ] Read and followed the [Contributing Guidelines](wiki_link).
+- [ ] Self-tested locally to ensure the code runs correctly and achieves expected results (all CI checks expected to pass).
+- [ ] Updated documentation if needed.
+- [ ] Verified accuracy or performance benchmarks if applicable.
+
+# Reviewers
+<!--
+Please note: each PR must be reviewed by at least **two committers** once all tests have passed.
+You may optionally tag members or contributors who might be interested in your PR.
+-->