GeezerVison

Thanks for the feedback on #2231. I've created this new PR, which merges into #2231, to address your comment. I will work on the changes and keep this PR's description up to date as I make progress.

Original PR: #2231
Triggering comment (#2231 (comment)):

🔵 Needs a closer look

A multiline block-comment sequence followed by code can still join a standalone comment run incorrectly and alter its indentation.

No open issues 🎉

1 previously missed issue
In code that hasn't changed since last review

Use the entire skipped comment group's end line for comparison
Rules/​UseConsistentIndentation.cs:512

NextTokenIgnoringComments can skip a block comment spanning additional lines, but this comparison uses only the first comment's end line. Inside an if block, a correctly indented # comment followed by unindented <# first #> <# second and then #> Write-Output 'value' is incorrectly grouped with that code-prefixed comment sequence, moving # comment from four to eight spaces. Compare against the end of the entire skipped comment group so comment-prefixed code stays outside the run.

1 resolved since last review

• Prevent repeated indentation of consecutive block comments

Review effort: Balanced

Copilot fix previously missed issue and create regression test for it. when finished open new PR for fix, if PR not possible push here directly