chore: develop -> master ff-only 머지 자동화 액션 추가

[whqtker]

• 라벨로 트리거

관련 이슈

• resolves:

작업 내용

특이 사항

리뷰 요구사항 (선택)

[coderabbitai]

Warning

Review limit reached

@whqtker, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 21 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 33565fd8-7753-47f8-9297-62c3be031cc4

📥 Commits

Reviewing files that changed from the base of the PR and between fdd6101 and 8cb7062.

📒 Files selected for processing (1)

• .github/workflows/ff-merge.yml

Walkthrough

이 PR은 ff-merge 워크플로우의 조건 검증 체계를 전면적으로 개편합니다. 다음과 같은 변경이 포함되어 있습니다:

1. 워크플로우 트리거 구성 변경
   • pull_request 이벤트에 labeled 액션 타입 추가
   • check_suite 이벤트 타입 처리 추가로 CI 완료 시 자동 실행 가능

2. PR 검증 조건 정의
   • 기존 review 기반 분기 제거
   • pull_request 이벤트 기준으로 base=master, head=develop, state=open 조건 확인
   • 조건 불만족 시 ready=false 즉시 반환

3. 승인 판정 메커니즘 전환
   • 리뷰 승인/변경요청 기반 로직 삭제
   • pulls.get API로 ready-to-merge 라벨 직접 조회
   • 라벨 부재 시 ready=false로 종료

4. 결과 메시지 문구 갱신
   • develop 변경 감지 실패 메시지를 "레이블 부착 이후 변경" 형태로 재구성

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested reviewers

• wibaek
• Hexeong
• JAEHEE25
• lsy1307
• sukangpunch
• Gyuhyeok99

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	설명에 필수 섹션 구조가 있으나 '작업 내용' 섹션이 비어있고 관련 이슈 번호가 미입력 상태입니다.	작업 내용 섹션에 라벨 기반 트리거 변경사항을 상세히 작성하고, 필요시 관련 이슈 번호를 명시해 주세요.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	제목이 PR의 주요 변경사항인 라벨 기반 ff-merge 자동화 액션 추가를 명확하게 설명합니다.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/label-based-ff-merge

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6512cd2cd4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/ff-merge.yml (1)

33-47: ⚡ Quick win

여러 개의 develop→master PR이 존재할 경우 예상치 못한 동작이 발생할 수 있습니다.

Line 46에서 prs[0]를 사용하여 첫 번째 PR만 처리하는데, 실제로 여러 개의 develop→master PR이 열려 있을 경우 어떤 PR이 선택될지 명확하지 않습니다. 정상적인 워크플로우에서는 하나의 PR만 존재해야 하지만, 방어적으로 처리하는 것을 권장합니다.

🛡️ 다중 PR 감지 및 경고 추가 제안

           if (prs.length === 0) {
             core.setOutput('ready', 'false');
             return;
           }
+
+          if (prs.length > 1) {
+            core.warning(`발견된 develop→master PR이 ${prs.length}개입니다. 첫 번째 PR(#${prs[0].number})을 사용합니다.`);
+          }

           prNumber = prs[0].number;

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/ff-merge.yml around lines 33 - 47, The current logic
assumes a single develop→master PR but uses prs[0], which is ambiguous when
multiple PRs exist; update the handling of the prs array in the block that sets
prNumber and headSha to detect multiple PRs (the prs variable and the assignment
to prNumber/headSha), and implement defensive behavior: if prs.length > 1, log
or warn (use core.warning or core.setOutput with a message), set
core.setOutput('ready','false') and return (or alternatively choose a
deterministic PR by sorting prs by created_at or number before selecting the top
candidate), otherwise continue to set prNumber = prs[0].number and headSha =
prs[0].head.sha as before. Ensure the change references prs, prNumber, and
headSha so reviewers can find the updated logic.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/ff-merge.yml:
- Around line 11-13: The workflow currently allows any PR labeled
"ready-to-merge" to trigger a fast-forward merge; restrict this by (1) limiting
who can apply that label at the repo/team level (enforce via GitHub settings)
and (2) add an explicit actor check in the actions/github-script verification
block (the step around lines 55-86) so that you only set ready=true when
github.event.label.sender or github.actor (the labeler) is in an allowlist (team
or user IDs) or has a required permission (e.g., MEMBER or MAINTAINER); update
the conditional that gates the merge (the if condition and the merge/push step
near lines 11-13 and 119-120) to require that verified ready flag, and finally
confirm branch protection settings so secrets.PAT pushes cannot bypass required
status checks or required reviewers.

---

Nitpick comments:
In @.github/workflows/ff-merge.yml:
- Around line 33-47: The current logic assumes a single develop→master PR but
uses prs[0], which is ambiguous when multiple PRs exist; update the handling of
the prs array in the block that sets prNumber and headSha to detect multiple PRs
(the prs variable and the assignment to prNumber/headSha), and implement
defensive behavior: if prs.length > 1, log or warn (use core.warning or
core.setOutput with a message), set core.setOutput('ready','false') and return
(or alternatively choose a deterministic PR by sorting prs by created_at or
number before selecting the top candidate), otherwise continue to set prNumber =
prs[0].number and headSha = prs[0].head.sha as before. Ensure the change
references prs, prNumber, and headSha so reviewers can find the updated logic.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ea14f3e-5ceb-4819-ba51-aac2f44295e3

📥 Commits

Reviewing files that changed from the base of the PR and between 7e070fe and fdd6101.

📒 Files selected for processing (1)

• .github/workflows/ff-merge.yml