Fixes #12638 - Fix broken examples#12639
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 409f1b6: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR attempts to fix broken examples in the Get-WinEvent cmdlet documentation across multiple PowerShell versions (5.1, 7.4, 7.5, 7.6). The primary focus was on fixing HTML entity encoding issues in XPath queries, but the changes introduce several critical bugs.
- Fixed HTML entity encoding display issues (but incorrectly changed the operator logic)
- Reformatted long lines for better readability
- Introduced incorrect file path references
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 17 comments.
| File | Description |
|---|---|
| reference/7.6/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md | Attempted to fix XPath operator encoding but changed logic from <= to >=, breaking the example; changed LogName to incorrect Logname casing |
| reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md | Same XPath operator issue; also introduced broken file paths by changing About folder to lowercase about and incorrectly lowercasing filenames; changed LogName to Logname; reformatted code indentation |
| reference/7.4/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md | XPath operator issue and line reformatting changes |
| reference/5.1/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md | XPath operator issue and line reformatting changes |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit cecedda: ✅ Validation status: passed
For more details, please refer to the build report. |
PR Summary
Fix broken examples
PR Checklist