diff options
| author | Russ White <russ@riw.us> | 2018-09-04 11:28:18 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-09-04 11:28:18 -0400 |
| commit | 1b7958c890b8685dc6721fbffb66f57b74afda0f (patch) | |
| tree | 20ddc84965d2d58b26ad45fec8961e9f8cce07dc | |
| parent | cefe81a9a0f9b3c70cf6b26ca251f537d6ae55b9 (diff) | |
| parent | 9119b9b11855e1801f9beee99c62eec5b5c73acb (diff) | |
Merge pull request #2939 from netravnen/feature/git-issue-teplate
Add ISSUE_TEMPLATE
| -rw-r--r-- | .github/ISSUE_TEMPLATE.md | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md new file mode 100644 index 0000000000..cedca17729 --- /dev/null +++ b/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,43 @@ +### 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! |
