Enhancement: Optimize Get-OriginalPRCommits to use PR commits directly

[rjmurillo-bot]

Origin

PR #202 comment 2639566878 from Copilot

Current Behavior

Get-OriginalPRCommits function:

1. Line 103: Fetches PR with gh pr view --json commits
2. Line 111: Queries ALL repository commits via gh api repos/.../commits and filters

This is inefficient on large repositories and may hit API rate limits.

Enhancement

Use the commits already retrieved from gh pr view:

$pr = gh pr view $PRNumber --json commits 2> | ConvertFrom-Json
if ($null -eq $pr -or -not $pr.commits) {
    return @()
}
return $pr.commits

Rationale

• Eliminates redundant API call
• Avoids rate limit risk on large repos
• Already have the data from line 103

Acceptance Criteria

• Remove redundant gh api call at line 111
• Return $pr.commits directly
• Verify Pester tests still pass
• Test on PR with >10 commits

[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 optimization of a PowerShell function in the PR workflow scripts to reduce API calls"
}

Roadmap Alignment

Based on the issue analysis:

**Issue Assessment:**
- **Type**: Code optimization (bug fix/enhancement hybrid)
- **Scope**: Single function in single file (`Get-OriginalPRCommits`)
- **Impact**: Medium (efficiency improvement, rate limit protection)
- **Complexity**: Low (clear implementation path, acceptance criteria defined)
- **Origin**: PR comment from Copilot (internal QA finding)

**Prioritization Analysis:**
- **KANO**: Performance feature (satisfaction proportional to implementation)
- **Urgency**: Low (current code works, just inefficient)
- **Dependencies**: None
- **Research**: None required (solution already specified)

**PRD Escalation Check:**
- Feature Request: No (optimization of existing function)
- Research Required: No (solution defined in issue)
- External Dependency: No
- Multi-Phase: No (single PR)
- Architectural Impact: No
- Customer-Facing: No (internal tool)

**Result**: Does not meet any PRD escalation criteria.

```json
{
  "milestone": "v1.1",
  "priority": "P2",
  "epic_alignment": "",
  "confidence": 0.85,
  "reasoning": "Code optimization with clear solution; aligns with v1.1 maintainability focus but no strategic epic match",
  "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

Related Issues

• Compare-DiffContent: Use OriginalCommits parameter for actual comparison #244
• Enhancement: Simplify jq pipeline in Get-CopilotAnnouncement #238
• DRY rate limit code #273

👤 Suggested Assignees

• rjmurillo-bot

---

🧪 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!