]> git.proxmox.com Git - mirror_frr.git/blame - .github/ISSUE_TEMPLATE.md
.github: Updated ISSUE_TEMPALTE.md
[mirror_frr.git] / .github / ISSUE_TEMPLATE.md
CommitLineData
cbb6b2a3 1### How to an submit issue
272fd0c3 2Please use this text as a template and replace text in the sections or remove
cbb6b2a3 3the entire section if it does not apply to your issue. For example in case of
9ab45012
C
4a question or feature request, just a description with some example is probably
5fine. Also remember to use GitHub Flavored Markdown properly, especially if
cbb6b2a3 6posting output or code listings.
272fd0c3
C
7
8### Things you may try first
cbb6b2a3
C
9(put "x" in "[ ]" if you already tried following)
10* [ ] Did you check if this is a duplicate issue?
11* [ ] Did you test it on the latest FRRouting/frr master branch?
272fd0c3
C
12
13**Related Issue:**
14[fill here if applicable]
15
16### Description
17[Description of the bug or feature]
18
19### Steps to Reproduce
201. [First Step]
212. [Second Step]
223. [and so on...]
23
24**Expected behavior:**
cbb6b2a3 25[What you expected to happen]
272fd0c3
C
26
27**Actual behavior:**
cbb6b2a3 28[What actually happened]
272fd0c3 29
cbb6b2a3 30### Components
272fd0c3
C
31[bgpd, build, doc, isisd, ospfd, etc.]
32
cbb6b2a3
C
33### Versions
34* OS: [name] [version]
35* Kernel: [Linux/BSD] [version]
36* FRR: [version]
37
272fd0c3 38### Attachments
9ab45012 39[Attach if applicable. For example log-files, log-lines. etc. etc.]
272fd0c3
C
40
41You're also welcomed to provide us with any other data you think may be useful.
42
43Thanks!