[Copilot]

• Problem: A block comment followed by executable code on the same line could be treated as part of an adjacent standalone comment run, producing an incorrect indentation offset.
• Change: Exclude such comments from run membership and offset calculations, preserving the executable line’s indentation.

if ($a) {
    # comment
        <# note #> Write-Output 'value'
}

The inline-comment line should be corrected to four spaces of indentation.

[Christoph Bergmeister (bergmeister)]

Copilot change this pr to a stacked pr because otherwise test suite won't run

[Copilot]

Christoph Bergmeister (@bergmeister) I've opened a new pull request, #2244, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

🟡 Changes recommended

The new logic loses continuation indentation and misses executable lines with multiple leading block comments.

2 open issues

• Preserve continuation indentation across standalone comments · New
• Skip multiple leading comments when detecting executable lines · New

What changed in this PR

This PR updates the indentation formatter to exclude block comments followed by same-line code from standalone comment runs, so executable lines receive normal indentation.

Changes:

• Adds same-line code checks when calculating comment-run membership and offsets.
• Adds a regression test for an over-indented executable line following a standalone comment.

File	Description
Tests/​Rules/​UseConsistentIndentation.tests.ps1	Tests indentation of a block comment followed by executable code.
Rules/​UseConsistentIndentation.cs	Excludes comments with following same-line code from comment-run calculations.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Pipeline indentation preservation regresses when an inline-code comment follows a standalone block comment separated by a line continuation.

1 open issue

• Preserve pipeline indentation across line continuations · New

2 resolved since last review

• Skip multiple leading comments when detecting executable lines
• Preserve continuation indentation across standalone comments

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Trailing comments can incorrectly propagate pipeline context and prevent indentation correction of an independent command.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Avoid inheriting pipeline context from trailing comments

Rules/​UseConsistentIndentation.cs:372

With PipelineIndentation = 'None', a function containing foo | bar # trailing followed by <# note #> baz leaves the independent baz command at eight spaces instead of correcting it to four. This condition accepts the trailing comment, so the recursive call incorrectly inherits pipeline context from the earlier pipe. Only inherit context from comments that start standalone lines, and add a regression test for this case.

1 resolved since last review

• Preserve pipeline indentation across line continuations

_{Review effort: Balanced}

[Christoph Bergmeister (bergmeister)]

Copilot fix this last unresolved review comment
Avoid inheriting pipeline context from trailing comments
Rules/​UseConsistentIndentation.cs:372

With PipelineIndentation = 'None', a function containing foo | bar # trailing followed by <# note #> baz leaves the independent baz command at eight spaces instead of correcting it to four. This condition accepts the trailing comment, so the recursive call incorrectly inherits pipeline context from the earlier pipe. Only inherit context from comments that start standalone lines, and add a regression test for this case.

[Copilot]

Copilot fix this last unresolved review comment
Avoid inheriting pipeline context from trailing comments
Rules/​UseConsistentIndentation.cs:372
...

Fixed in 80a3db7. Pipeline context is inherited only from comments that start standalone lines. Added the regression test; all 105 indentation tests pass, and CodeQL reports no alerts.

Copilot change this pr to a stacked pr because otherwise test suite won't run

Confirmed this PR is already stacked on copilot/fix-psuseconsistentindentation-issue. Its latest CI Tests run passed.

[Copilot]

🔵 Needs a closer look

The interaction between inherited continuation context and executable-line indentation needs human validation before approval.

No open issues 🎉

_{Review effort: Balanced}