[Copilot]

Fallback DSC AST detection could pair executable commands with following blocks, suppressing expected Get- corrections when the block had redirections or a semicolon separated the statements.

• Detection: Reject candidate blocks with redirections and sibling statements separated by a statement terminator.
• Regression coverage: Verify both commands below retain their Get-ChildItem corrections.

{
    gci .
    {} > $null
    gci .; {}
}

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

2 open issues

• Parsing the separator substring with Parser.ParseInput can be relatively expensive if this code… · New
• The method name HasStatementTerminator is misleading because the implementation only checks for… · New

What changed in this PR

Updates DSC resource-body detection to avoid incorrectly pairing commands with subsequent script blocks when redirections or semicolon-separated statements are present, ensuring alias corrections still occur as expected.

Changes:

• Reject candidate DSC “resource body” blocks when the candidate scriptblock expression has redirections.
• Reject candidate DSC “resource body” blocks when a semicolon statement separator exists between the command and the following block.
• Add regression test ensuring gci is still flagged/corrected in the reported edge cases.

File	Description
Tests/​Rules/​AvoidUsingAlias.tests.ps1	Adds regression coverage for alias correction when adjacent blocks include redirections or are separated by semicolons.
Rules/​AvoidAlias.cs	Tightens DSC AST fallback pairing logic by rejecting redirection-bearing blocks and semicolon-separated statements.

_{Review effort: Lite}

[Copilot]

🟢 Approval recommended

No active review issues remain for the fallback DSC resource-body detection changes.

No open issues 🎉

2 resolved since last review

• Parsing the separator substring with Parser.ParseInput can be relatively expensive if this code…
• The method name HasStatementTerminator is misleading because the implementation only checks for…

_{Review effort: Balanced}