Merge pull request #4048 from FRRouting/qlyoung-patch-1

Update issue templates
This commit is contained in:
Russ White 2019-03-31 17:01:57 -04:00 committed by GitHub
commit 6b74e55666
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 43 additions and 52 deletions

View File

@ -1,52 +0,0 @@
# HOW TO GET YOUR ISSUE ADDRESSED FASTER
* When reporting a crash provide a backtrace
* When pasting configs, logs, shell output, backtraces, and other large chunks
of text [use Markdown code blocks](https://github.github.com/gfm/#fenced-code-blocks)
* Include the FRR version; if you built from Git, please provide the commit
hash
* Write your issue in English
### How to submit an issue
Please use this text as a template and replace text in the sections or remove
the entire section if it does not apply to your issue. For example in case of
a question or feature request, just a description with some example is probably
fine. Also remember to use GitHub Flavored Markdown properly, especially if
posting output or code listings.
### Things you may try first
(put "x" in "[ ]" if you already tried following)
* [ ] Did you check if this is a duplicate issue?
* [ ] Did you test it on the latest FRRouting/frr master branch?
**Related Issue:**
[fill here if applicable]
### Description
[Description of the bug or feature]
### Steps to Reproduce
1. [First Step]
2. [Second Step]
3. [and so on...]
**Expected behavior:**
[What you expected to happen]
**Actual behavior:**
[What actually happened]
### Components
[bgpd, build, doc, isisd, ospfd, etc.]
### Versions
* OS: [name] [version]
* Kernel: [Linux/BSD] [version]
* FRR: [version]
### Attachments
[Attach if applicable. For example log-files, log-lines. etc. etc.]
You're also welcomed to provide us with any other data you think may be useful.
Thanks!

43
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@ -0,0 +1,43 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: triage
assignees: ''
---
- When reporting a crash, provide a backtrace
- When pasting configs, logs, shell output, backtraces, and other large chunks of text use Markdown code blocks
- Include the FRR version; if you built from Git, please provide the commit hash
- Write your issue in English
---------------
**Describe the bug**
A clear and concise description of what the bug is.
(put "x" in "[ ]" if you already tried following)
[ ] Did you check if this is a duplicate issue?
[ ] Did you test it on the latest FRRouting/frr master branch?
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Versions**
- OS Kernel: [e.g. Linux, OpenBSD, etc] [version]
- FRR Version [version]
**Additional context**
Add any other context about the problem here.