yaml withspace matters
mention markdown syntax on how to best represent withespace.
This commit is contained in:
6
.github/issue_template.md
vendored
6
.github/issue_template.md
vendored
@@ -1,6 +1,12 @@
|
|||||||
<!--- Provide a general summary of the issue in the Title above -->
|
<!--- Provide a general summary of the issue in the Title above -->
|
||||||
<!--- https://guides.github.com/features/mastering-markdown/#examples -->
|
<!--- https://guides.github.com/features/mastering-markdown/#examples -->
|
||||||
|
|
||||||
|
<!--- 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
|
## Expected Behavior
|
||||||
<!--- If you're describing a bug, tell us what should happen -->
|
<!--- If you're describing a bug, tell us what should happen -->
|
||||||
<!--- If you're suggesting a change/improvement, tell us how it should work -->
|
<!--- If you're suggesting a change/improvement, tell us how it should work -->
|
||||||
|
|||||||
Reference in New Issue
Block a user