Skip to content

fix: promote-to-prod가 GITHUB_TOKEN 연쇄 트리거 제약에 막히던 문제 수정 - #242

Merged
unam98 merged 1 commit into
mainfrom
fix/promote-workflow-token-chain
Aug 11, 2026
Merged

fix: promote-to-prod가 GITHUB_TOKEN 연쇄 트리거 제약에 막히던 문제 수정#242
unam98 merged 1 commit into
mainfrom
fix/promote-workflow-token-chain

Conversation

@unam98

Copy link
Copy Markdown
Collaborator

작업 배경

#241 머지 직후 v0.0.1로 실제 테스트했는데, 태그는 정상 push됐지만 prod-cd.yml이 트리거되지 않았다. 원인: GitHub Actions는 기본 GITHUB_TOKEN으로 push된 이벤트가 다른 워크플로를 연쇄 실행시키지 않도록 막아둔다(무한루프 방지) — promote-to-prod.yml이 정확히 이 케이스였다.

변경 사항

영역내용
prod-cd.ymlon.workflow_dispatch 트리거 추가 (기존 on.push.tags는 유지 — 로컬에서 직접 태그 push하는 경우 대비)
promote-to-prod.yml태그 push 직후 gh workflow run prod-cd.yml --ref <태그>로 명시적 호출 추가, permissions.actions: write 추가

영향 범위

  • Promote to Production 워크플로를 실행해야만 발생하는 변경 — 다른 워크플로/배포 경로에 영향 없음

Test Plan

  • YAML 문법 검증
  • 실제로 Promote to Production 재실행해서 prod-cd.yml이 트리거되는지 확인 (이 PR 병합 직후 진행)

🤖 Generated with Claude Code

v0.0.1 태그로 실제 테스트해보니 태그는 push됐지만 prod-cd.yml이
트리거되지 않았다. GitHub Actions는 기본 GITHUB_TOKEN으로 push된
이벤트가 다른 워크플로를 연쇄 실행시키지 않도록 막아두기 때문
(무한루프 방지) — promote-to-prod.yml이 정확히 이 케이스였다.
prod-cd.yml에 workflow_dispatch 트리거를 추가하고, promote-to-prod.yml이
태그 push 직후 `gh workflow run prod-cd.yml --ref <태그>`로 명시적으로
호출하도록 바꿔서 우회했다.
@unam98unam98 self-assigned this Aug 11, 2026
@coderabbitai

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in:35 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 55031049-1bbb-4cb4-ab59-7ec0a6e7d9e5

📥 Commits

Reviewing files that changed from the base of the PR and between c4b1f6a and e98d5a1.

📒 Files selected for processing (2)
  • .github/workflows/prod-cd.yml
  • .github/workflows/promote-to-prod.yml

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

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

@unam98
unam98 merged commit d7e6d11 into mainAug 11, 2026
2 checks passed
@unam98
unam98 deleted the fix/promote-workflow-token-chain branch August 11, 2026 08:36
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@unam98@alh0409