Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit d96e02a

Browse files
rjmholtTylerLeonhardt
authored andcommittedOct 23, 2018
[Ignore] Update PSSA bug report template for flexibility (#1588)
* [Ignore] Update PSSA bug report template for flexibility Address @codykonior's feedback on bug template * if -> whether
1 parent db76d05 commit d96e02a

File tree

1 file changed

+23
-3
lines changed

1 file changed

+23
-3
lines changed
 
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,28 @@
11
---
22
name: Script analysis or formatting bug report 🚦🖌️
3-
about: Script analysis and formatting are provided by PSScriptAnalyzer, whose issues are tracked in a different GitHub repository.
3+
about: Script analysis and formatting are provided by PSScriptAnalyzer. Before submitting a script analysis or formatting issue, check to see whether the issue lies with PSScriptAnalyzer or with the VSCode PowerShell extension.
44

55
---
66

7-
* Please submit script analysis and formatting issues to the
8-
[PSScriptAnalyzer](https://github.com/powershell/PSScriptAnalyzer/issues) repo on GitHub.
7+
<!--
8+
9+
Before submitting a formatting or script analysis issue,
10+
please check the relevant PSScriptAnalyzer command in a PowerShell console *outside* of VSCode.
11+
12+
Script analysis issues:
13+
```powershell
14+
Invoke-ScriptAnalyzer -Path './path/to/your/script.ps1'
15+
```
16+
17+
Formatting issues:
18+
```powershell
19+
Get-Content -Raw './path/to/your/script.ps1' | Invoke-Formatter
20+
```
21+
22+
If the problem occurs in the console, please submit a new issue with [PSScriptAnalyzer](https://github.com/powershell/PSScriptAnalyzer/issues).
23+
24+
If it does not occur in the console, it may be a PowerShell extension bug -- please open an issue here.
25+
26+
(For information on using the PSScriptAnalyzer module, see [here](https://github.com/PowerShell/PSScriptAnalyzer#usage))
27+
28+
-->

0 commit comments

Comments
 (0)
Please sign in to comment.