Enhancement: Add PR number validation to Copilot follow-up detection

[rjmurillo-bot]

Origin

PR #202 comment 2639354259 from Copilot

Current Behavior

Pattern regex uses \d+ to match any digits in branch name copilot/sub-pr-{number}.

No validation that extracted number matches the original PR number parameter.

Enhancement

Validate extracted PR number:

if ($headRef -match 'copilot/sub-pr-(\d+)') {
    $extractedPR = [int]$matches[1]
    return $extractedPR -eq $PRNumber
}
return $false

Rationale

Prevents false positives if repository has multiple Copilot follow-up branches.

Acceptance Criteria

• Extract PR number from branch name
• Compare against $PRNumber parameter
• Return false if mismatch
• Add Pester test for validation logic

[github-actions]

AI Triage Summary

Note

This issue has been automatically triaged by AI agents

What is AI Triage?

This issue was analyzed by AI agents:

• Analyst Agent: Categorizes the issue and suggests appropriate labels
• Roadmap Agent: Aligns the issue with project milestones and priorities
• Explainer Agent (if escalated): Generates comprehensive PRD

Triage Results

Property	Value
Category	enhancement
Labels	["enhancement","area-workflows"]
Priority	P2
Milestone	v1.1

Categorization Analysis

{
  "labels": ["enhancement", "area-workflows"],
  "category": "enhancement",
  "confidence": 0.92,
  "reasoning": "Issue requests validation improvement for Copilot follow-up branch detection in workflow scripts, with specific PowerShell implementation and Pester test criteria."
}

Roadmap Alignment

Based on roadmap analysis:

- This is a targeted bug fix / hardening enhancement for existing CI automation
- No epic alignment (doesn't fit VS Code Consolidation or Pre-PR Security Gate)
- Small scope: single file change + Pester test
- No research required, clear implementation path
- Internal tooling improvement, not customer-facing

```json
{
  "milestone": "v1.1",
  "priority": "P2",
  "epic_alignment": "",
  "confidence": 0.85,
  "reasoning": "Standard enhancement to CI tooling with clear implementation path and acceptance criteria",
  "escalate_to_prd": false,
  "escalation_criteria": [],
  "complexity_score": 0
}

---

_{Powered by AI Issue Triage - View Workflow}

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Enhancement: Stricter pattern matching in Detect-CopilotFollowUpPR #236

Related Issues

• feat: Enhance pr-comment-responder to handle Copilot's follow-up PR pattern #2
• Compare-DiffContent: Use OriginalCommits parameter for actual comparison #244
• Add integration tests for Compare-DiffContent function #240
• Enhancement: Optimize Get-OriginalPRCommits to use PR commits directly #290

🔗 Related PRs

rjmurillo/moq.analyzers#426 - Strengthen Copilot instructions [merged]
rjmurillo/moq.analyzers#552 - Update copilot instructions for PR checks and CI [merged]

👤 Suggested Assignees

• rjmurillo-bot
• rjmurillo

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!