update .github (#4653)

* Update PULL_REQUEST_TEMPLATE.md (#2639)

Signed-off-by: jinhai <hai.jin@zilliz.com>

* optimize config code (#2996)

* update

Signed-off-by: wxyu <xy.wang@zilliz.com>

* update pull request template

Signed-off-by: wxyu <xy.wang@zilliz.com>

* [skip ci] update pull request template (#3008)

Signed-off-by: wxyu <xy.wang@zilliz.com>

* [skip ci] Update PR template

Signed-off-by: jinhai <hai.jin@zilliz.com>

* update PULL_REQUEST_TEMPLATE.md

Signed-off-by: shengjun.li <shengjun.li@zilliz.com>

* [skip ci] Update ISSUE template

Signed-off-by: jinhai <hai.jin@zilliz.com>

* [skip ci]fix template doc (#3268)

Signed-off-by: shengjun.li <shengjun.li@zilliz.com>

* [skip ci]update issue template (#3379)

Signed-off-by: Wang Xiangyu <xy.wang@zilliz.com>

* [skip ci]remove cherry-pick section in PULL REQUEST TEMPLATE (#3571)

Signed-off-by: Wang Xiangyu <xy.wang@zilliz.com>

* [skip ci] add enhancement issue template (#3585)

Signed-off-by: yudong.cai <yudong.cai@zilliz.com>

Co-authored-by: Jin Hai <hai.jin@zilliz.com>
Co-authored-by: Wang XiangYu <xy.wang@zilliz.com>
Co-authored-by: Cai Yudong <yudong.cai@zilliz.com>
pull/4673/head
shengjun.li 2021-01-23 11:06:42 +08:00 committed by GitHub
parent f942f0b823
commit 893e8bb020
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 54 additions and 20 deletions

View File

@ -7,6 +7,8 @@ assignees: ''
---
**Please state your issue using the following template and, most importantly, in English.**
**Describe the bug**
A clear and concise description of what the bug is.
@ -16,11 +18,24 @@ Follow this [guide](http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-r
**Expected behavior**
A clear and concise description of what you expected to happen.
**Method of installation**
- [ ] Docker/cpu
- [ ] Docker/gpu
- [ ] Build from source
**Environment details**
- Hardware/Softward conditions (OS, CPU, GPU, Memory)
- Method of installation (Docker, or from source)
- Milvus version (v0.3.1, or v0.4.0)
- Milvus configuration (Settings you made in `server_config.yaml`)
- Hardware/Softwars conditions (OS, CPU, GPU, Memory)
- Milvus version (master or released version)
**Configuration file**
Settings you made in `server_config.yaml` or `milvus.yaml`
```yaml
paste-file-content-here
```
**Screenshots**
If applicable, add screenshots to help explain your problem.

5
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View File

@ -0,0 +1,5 @@
blank_issues_enabled: false
contact_links:
- name: Ask a question
url: https://github.com/milvus-io/milvus/discussions
about: Ask questions and discuss with other community members

View File

@ -7,7 +7,7 @@ assignees: ''
---
## Report incorrect documentation
**Please state your issue using the following template and, most importantly, in English.**
**Location of incorrect documentation**
Provide links and line numbers if applicable.

15
.github/ISSUE_TEMPLATE/enhancement.md vendored Normal file
View File

@ -0,0 +1,15 @@
---
name: "Enhancement request"
about: Suggest an enhancement idea for Milvus
title: ''
labels: ''
assignees: ''
---
**Please state your issue using the following template and, most importantly, in English.**
**What would you like to be added ?**
**Why is this needed ?**

View File

@ -7,6 +7,8 @@ assignees: ''
---
**Please state your issue using the following template and, most importantly, in English.**
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. E.g. I wish I could use Milvus to do [...]

View File

@ -1,10 +0,0 @@
---
name: "\U0001F914 General question"
about: Ask a general question about Milvus
title: ''
labels: ''
assignees: ''
---
**What is your question?**

View File

@ -1,18 +1,25 @@
**What type of PR is this?**
api-change / bug / design / documentation / feature
**What this PR does / why we need it:**
- [ ] API-change
- [ ] BUG
- [ ] Improvement
- [ ] Documentation
- [ ] Feature
- [ ] Test and CI
- [ ] Code Refactoring
**Which issue(s) this PR fixes:**
Fixes #
**What this PR does / why we need it:**
Not Available
**Special notes for your reviewer:**
Not Available
**Additional documentation (e.g. design docs, usage docs, etc.):**
Not Available