🧹 코드 건강성 개선: PR 헤드 검증 로직 중복 제거

[seonghobae]

🎯 What: pr_review_merge_scheduler.py 파일의 dismiss_stale_opencode_approvals, dismiss_stale_opencode_change_requests, restamp_pr_head_for_last_push_approval 함수에 중복되어 있던 PR 헤드 검증 및 GitHub API 호출 로직을 require_unmodified_pr_head라는 헬퍼 함수로 추출했습니다.
💡 Why: 동일한 코드 블록이 3곳에서 사용되어 코드 길이가 길어지고 유지보수성이 떨어졌습니다. 헬퍼 함수를 통해 코드 중복을 제거하고 가독성을 높였습니다.
✅ Verification: 단위 테스트와 coverage 검사를 모두 통과했으며, interrogate로 docstring 커버리지 100%를 유지함을 확인했습니다.
✨ Result: pr_review_merge_scheduler.py 내 복잡한 함수의 코드 크기가 줄어들고 오류 메시지 포맷이 통일되어 전체적인 코드 건강성이 향상되었습니다.

---

PR created automatically by Jules for task 8856118095832387920 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d2a5eb4a-676c-4e9c-8828-a5d8c5898912

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 0535a8c.

📒 Files selected for processing (3)

• scripts/ci/pr_review_merge_scheduler.py
• tests/test_opencode_existing_approval_gate.py
• tests/test_opencode_security_boundaries.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

RCA/feasibility: closing unmerged as structurally superseded by #828. This refactor extracts repeated live-head validation from the pre-#828 monolithic scheduler and changes tests around that old layout. #828 is the authoritative security repair for scheduler merge authorization and replaces that monolith with an independent-approval policy facade plus _pr_review_merge_scheduler_core.py; head validation/dismissal behavior must be evaluated in that protected architecture, not merged as a parallel old-layout refactor. No distinct current correctness defect is demonstrated here. Reassess duplication only after #828 integrates and exact-head safety/runtime evidence is stable.

[google-labs-jules]

RCA/feasibility: closing unmerged as structurally superseded by #828. This refactor extracts repeated live-head validation from the pre-#828 monolithic scheduler and changes tests around that old layout. #828 is the authoritative security repair for scheduler merge authorization and replaces that monolith with an independent-approval policy facade plus _pr_review_merge_scheduler_core.py; head validation/dismissal behavior must be evaluated in that protected architecture, not merged as a parallel old-layout refactor. No distinct current correctness defect is demonstrated here. Reassess duplication only after #828 integrates and exact-head safety/runtime evidence is stable.

Understood. Acknowledging that this work is structurally superseded by #828 and stopping work on this task.