Uh oh!
There was an error while loading. Please reload this page.
ci: 상용 배포 트리거를 main push에서 git tag(v*)로 분리 - #240
Conversation
지금까지는 main push마다 staging(Render)과 상용(AWS CodeDeploy)이 동시에 배포됐다. staging에서 검증할 시간 없이 merge=상용 반영이라 안전망이 없는 구조였다. 이제 staging은 main push에 그대로 자동 배포되고, 상용은 v로 시작하는 git tag를 push해야 배포되도록 분리했다(Continuous Delivery). merge → staging 확인 → 태그 push 순서로 상용 반영.
Warning Review limit reached
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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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. Comment |
Uh oh!
There was an error while loading. Please reload this page.
작업 배경
Trunk-Based Development 전환(#236) 이후 staging(Render)과 상용(AWS CodeDeploy)이 둘 다
mainpush에 트리거돼서, merge하면 검증 없이 바로 상용까지 나가는 문제가 있었다. Continuous Delivery 패턴(merge는 항상 배포 가능한 상태만 보장, 상용 반영은 명시적 트리거)으로 분리한다.변경 사항
prod-cd.ymlpush: branches: [main]→push: tags: ['v*']로 변경README.md영향 범위
main에 push/merge해도 상용에 자동 반영되지 않는다. staging은 그대로 자동 배포됨.git tag v1.x.x && git push origin v1.x.x필요.dev→main으로 바꿔야 함(진행 중).Test Plan
buildCI 통과로 workflow 파일 자체는 파싱됨)🤖 Generated with Claude Code