Skip to content

ci: 상용 배포 트리거를 main push에서 git tag(v*)로 분리 - #240

Merged
unam98 merged 1 commit into
mainfrom
ci/prod-cd-tag-trigger
Aug 11, 2026
Merged

ci: 상용 배포 트리거를 main push에서 git tag(v*)로 분리#240
unam98 merged 1 commit into
mainfrom
ci/prod-cd-tag-trigger

Conversation

@unam98

Copy link
Copy Markdown
Collaborator

작업 배경

Trunk-Based Development 전환(#236) 이후 staging(Render)과 상용(AWS CodeDeploy)이 둘 다 main push에 트리거돼서, merge하면 검증 없이 바로 상용까지 나가는 문제가 있었다. Continuous Delivery 패턴(merge는 항상 배포 가능한 상태만 보장, 상용 반영은 명시적 트리거)으로 분리한다.

변경 사항

영역내용
prod-cd.yml트리거를 push: branches: [main]push: tags: ['v*']로 변경
README.md배포 전략 섹션 추가 (staging/상용 트리거 분리 표, 태그 배포 절차)

영향 범위

  • 이후로는 main에 push/merge해도 상용에 자동 반영되지 않는다. staging은 그대로 자동 배포됨.
  • 상용에 반영하려면 git tag v1.x.x && git push origin v1.x.x 필요.
  • staging 배포(Render)는 이 PR과 무관 — 별도로 Render 대시보드 배포 트리거 branch를 devmain으로 바꿔야 함(진행 중).

Test Plan

  • YAML 문법 확인 (build CI 통과로 workflow 파일 자체는 파싱됨)
  • 실제 태그 push로 상용 배포가 트리거되는지는 다음 릴리즈 때 확인 필요

🤖 Generated with Claude Code

지금까지는 main push마다 staging(Render)과 상용(AWS CodeDeploy)이
동시에 배포됐다. staging에서 검증할 시간 없이 merge=상용 반영이라
안전망이 없는 구조였다.
이제 staging은 main push에 그대로 자동 배포되고, 상용은 v로
시작하는 git tag를 push해야 배포되도록 분리했다(Continuous
Delivery). merge → staging 확인 → 태그 push 순서로 상용 반영.
@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:4 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: ffeec48c-a709-42fa-adb8-999c8ecb2297

📥 Commits

Reviewing files that changed from the base of the PR and between 74c0679 and ae07098.

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

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 24ed6ba into mainAug 11, 2026
2 checks passed
@unam98
unam98 deleted the ci/prod-cd-tag-trigger branch August 11, 2026 08:08
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