135/netdisco
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

netdisco-docker triage

Browse Source 
point netdisco docker users to the docker issue tracker as a first step, so we can spent less time on triaging issues.

netdisco docker has some quirks not present in regular netdisco, if it turns out to be non container related we can always move the issue back to this tracker.

btw, seems we need to change our issue templates, but only project admins can do so:
"You are using an old version of issue templates. Please update to the new issue template workflow. Learn more."
-> https://help.github.com/articles/about-issue-and-pull-request-templates
This commit is contained in:
nick n
2019-07-19 01:14:27 +02:00
committed by GitHub
parent f1891be307
commit 5b9761cbae
1 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
.github/issue_template.md vendored
View File

@@ -1,17 +1,23 @@
<!--- Provide a general summary of the issue in the Title above -->
<!---
Provide a general summary of the issue in the Title above
<!-- stop! If your ticket is about a device not being detected correctly, -->
<!-- see SNMP::Info: https://github.com/netdisco/snmp-info/issues/new -->
STOP! If your ticket is about a device not being detected correctly,
see SNMP::Info: https://github.com/netdisco/snmp-info/issues/new
<!-- stop! If you have new MIBs to submit, -->
<!-- see netdisco-mibs: https://github.com/netdisco/netdisco-mibs/issues/new -->
STOP! If you have new MIBs to submit,
see netdisco-mibs: https://github.com/netdisco/netdisco-mibs/issues/new
<!-- everything else about Netdisco's behaviour is good, here :-D -->
STOP! If you are running a netdisco docker setup,
see netdisco-docker: https://github.com/netdisco/netdisco-docker/issues/new
everything else about Netdisco's behaviour is good, here :-D
when including netdisco config snippets, whitespace matters since it's a yaml file
for github issues it really helps if you include the relevant config parts in a codeblock (code fencing)
see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that)
this should preserve spaces in the issue tracker and make troubleshooting quicker
-->
<!--- when including netdisco config snippets, whitespace matters since it's a yaml file -->
<!--- for github issues it really helps if you include the relevant config parts in a codeblock (code fencing) -->
<!--- see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that) -->
<!--- this should preserve spaces in the issue tracker and make troubleshooting quicker -->
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->