Merge branch 'pr_1379'

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,50 +0,0 @@
-name: Bug report
-description: bug report for OceanBase
-title: "[Bug]: "
-labels: [bug]
-assignees:
-  - caifeizhi
-body:
-  - type: checkboxes
-    attributes:
-      label: Please check the issue list for the same bug 
-      options:
-        - label: Please checked issue list and confirm this bug is encountered for the first time.
-          required: true
-        - label: Please try full text in English and attach precise description.
-          required: true
-  - type: textarea
-    attributes:
-      label: Environment
-      description: |
-        Environment Details sometimes important 
-      value: |
-        - OB Version&commit_id or other module version&commit_id (e.g. observer V3.1.2 8b23a93):
-        - Hardware parameter:OS type & Compliler & CPU etc. 
-        - Others
-      render: markdown
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Fast Reproduce Steps(Required)
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Actual Behavior
-      description: What is the result? picture is allowed
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Expected Behavior
-      description: what you expected.
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: other information
-      description: Error Log or Core stack or Others
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: 🐞 Bug report
+about: Create a report to help us improve
+title: "[Bug]: <title>"
+labels: ["type: bug"]
+---
+
+**Describe the bug**
+<!-- A clear and concise description of bug. -->
+
+** Environment**
+<!-- Environment Details sometimes important -->
+- OS Version and CPU Arch(`uname -a`):
+  
+- OB Version(`LD_LIBRARY_PATH=../lib:$LD_LIBRARY_PATH ./observer -V`):
+  
+
+**Fast Reproduce Steps(Required)**
+
+Steps to reproduce the behavior:
+
+**Expected behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Actual Behavior**
+<!-- What is the result? picture is allowed -->
+
+**Additional context**
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/enhancement.md

@@ -0,0 +1,7 @@
+---
+name: 🌟 Enhancement
+about: I want to make an enhancement.
+labels: ["type: enhancement"]
+---
+
+**Enhancement**

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: 🚀 Feature Request
+description: Suggest an idea for this project
+title: "[feat.]: <title>"
+labels: ["type: feature"]
+---
+
+**Use Case**
+<!-- A clear and concise description of what is the intended usage scenario is. -->
+
+**Describe the solution you'd like**
+<!-- A clear and concise description of what you want to happen. -->
+
+**Describe alternatives you've considered**
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+**Additional context**
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,26 +0,0 @@
-name: feature request
-description: feature request for OceanBase
-title: "[feat.]: "
-labels: [feature]
-assignees:
-  - caifeizhi
-body:
-  - type: checkboxes
-    attributes:
-      label: Please check the issue list for the same feature first
-      options:
-        - label: Please checked issue list and confirm this feature is encountered for the first time.
-          required: true
-        - label: Please try full text in English and attach precise description.
-          required: true
-  - type: textarea
-    attributes:
-      label: A full description of the feature and provide some example if the same feature exists in other products, such as mysql  
-      render: markdown
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: other information
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,16 @@
+---
+name: 🙋 Question
+about: I have a question.
+title: "[Question]: "
+labels: ["type: question"]
+---
+
+If the question is concise and probably has a short answer, asking it in [community Slack](https://join.slack.com/t/oceanbase/shared_invite/zt-1e25oz3ol-lJ6YNqPHaKwY_mhhioyEuw)
+
+**Question**
+
+**Environment**
+
+- OS Version and CPU Arch(`uname -a`):
+
+- OB Version(`LD_LIBRARY_PATH=../lib:$LD_LIBRARY_PATH ./observer -V`):

.github/ISSUE_TEMPLATE/question.yml

@@ -1,25 +0,0 @@
-name: question
-description: concise description of the problem.
-title: "[Question]: "
-labels: [question]
-assignees:
-  - caifeizhi
-body:
-  - type: checkboxes
-    attributes:
-      label: Please check the issue list for the same question
-      options:
-        - label: Please try full text in English and attach precise description.
-          required: true
-  - type: markdown
-    attributes:
-      value: |
-        Make sure you have:
-        * Searched [GitHub issue](https://github.com/oceanbase/oceanbase/issues)
-        * Searched [documentation](https://open.oceanbase.com)
-  - type: textarea
-    attributes:
-      label: Describe your question
-      description: better to provide some pictures.
-    validations:
-      required: true

.github/pull_request_template.md

@@ -1,53 +1,34 @@
 <!--
-Thank you for contributing to **OceanBase**! Please read the [How to Contribute](https://github.com/oceanbase/oceanbase/wiki/how_to_contribute) document **BEFORE** filing this PR.
+Thank you for contributing to **OceanBase**! 
+Please read the [How to Contribute](https://github.com/oceanbase/oceanbase/wiki/how_to_contribute) document **BEFORE** filling this PR.
+
+**If this pull request have a significant impact, please make sure you have discussed with OceanBase group.**
 -->
 
-### What changes were proposed in this pull request?
+### Task Description
 
 <!--
-Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
-If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
-  1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
-  2. If you fix some nGQL features, you can provide some references.
-  3. If there is design documentation, please add the link.
-  4. If there is a discussion in the mailing list, please add the link.
+The problem you resolved by this pull request.
+You can link the issue via the "close #xxx" or "ref #xxx".
 -->
 
-### Why are the changes needed?
+### Solution Description
 
+<!-- Please clearly and consice descipt the solution. -->
+
+### Passed Regressions
+
+<!-- Unittest, mysql test or test it manually? -->
+
+### Upgrade Compatibility
+
+<!-- Please make sure this is compatible with old version or you should give us upgrading solution. -->
+
+### Other Information
+
+<!-- Any information helping to review this pull request. -->
+
+### Release Note
 <!--
-Please clarify why the changes are needed. For instance,
-  1. If you propose a new API, clarify the use case for a new API.
-  2. If you fix a bug, you can clarify why it is a bug.
+A concise release note can help users to understand how your pull request makes difference.
 -->
-
-### Will break the compatibility? How if so?
-
-<!--
-Please make sure it do not break the system compatibility, such as
-  1. nGQL grammar changes;
-  2. RPC protocol can't be compatible with previous;
-  3. Storage format; etc.
--->
-
-### Does this PR introduce any user-facing change?
-
-<!--
-If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description and/or an example to show the behavior difference if possible.
-If no, write 'No'.
--->
-
-### How was this patch tested?
-
-<!--
-If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
-If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
-If tests were not added, please describe why they were not added and/or why it was difficult to add.
--->
-
-### Checklist
-<!--Tick the checkbox(es) below to choose what you have done.-->
-
-- [ ] I've run the tests to see all new and existing tests pass.
-- [ ] If this Pull Request resolves an issue, I linked to the issue in the text above.
-- [ ] I've informed the technical writer about the documentation change if necessary.