[Docs] Add PR template and modify issue template (#380)

* Add language suggestion in issue-template

* Add issue template config

* Add PR template

* Update pr template according to mmcv #1228
pull/397/head
Ma Zerun 2021-08-04 14:30:20 +08:00 committed by GitHub
parent ade7b80e44
commit 2aa4100595
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 46 additions and 30 deletions

View File

@ -7,6 +7,8 @@ assignees: ''
---
推荐使用英语模板 General question以便你的问题帮助更多人。
### 首先确认以下内容
- 我已经查询了相关的 issue但没有找到需要的帮助。
- 我已经阅读了相关文档,但仍不知道如何解决。

View File

@ -7,14 +7,16 @@ assignees: ''
---
推荐使用英语模板 Feature request以便你的问题帮助更多人。
### 描述这个功能
[填写这里]
### 动机
请简要说明以下为什么需要添加这个新功能
例1. 现在进行 xxx 的时候不方便
例2. 最近的论文中提出了有一个很有帮助的 xx
1. 现在进行 xxx 的时候不方便
2. 最近的论文中提出了有一个很有帮助的 xx
[填写这里]

View File

@ -7,6 +7,8 @@ assignees: ''
---
推荐使用英语模板 Bug report以便你的问题帮助更多人。
### 描述 bug
简单地描述一下遇到了什么 bug

View File

@ -1,28 +0,0 @@
---
name: 提问
about: 遇到问题并寻求帮助
title: ''
labels: help wanted
assignees: ''
---
### 首先确认以下内容
- 我已经查询了相关的 issue但没有找到需要的帮助。
- 我已经阅读了相关文档,但仍不知道如何解决。
### 描述你遇到的问题
[填写这里]
### 相关信息
1. `pip list | grep "mmcv\|mmcls\|^torch"` 命令的输出
[填写这里]
2. 如果你修改了,或者使用了新的配置文件,请在这里写明
```python
[填写这里]
```
3. 如果你是在训练过程中遇到的问题,请填写完整的训练日志和报错信息
[填写这里]
4. 如果你对 `mmcls` 文件夹下的代码做了其他相关的修改,请在这里写明
[填写这里]

View File

@ -0,0 +1,6 @@
blank_issues_enabled: false
contact_links:
- name: MMClassification Documentation
url: https://mmclassification.readthedocs.io/en/latest/
about: Check if your question is answered in docs

View File

@ -0,0 +1,32 @@
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
## Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
## Modification
Please briefly describe what modification is made in this PR.
## BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
## Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
## Checklist
**Before PR**:
- [ ] Pre-commit or other linting tools are used to fix the potential lint issues.
- [ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
- [ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
- [ ] The documentation has been modified accordingly, like docstring or example tutorials.
**After PR**:
- [ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
- [ ] CLA has been signed and all committers have signed the CLA in this PR.