Fix/vercel build#379
Conversation
- Vercel GitHub Integration already handles main branch deployments - Remove redundant custom deployment workflow - Keep headver-tagging for version management if needed separately
- Remove vercel link step and use VERCEL_ORG_ID/PROJECT_ID env vars - Add .vercel directory cleanup to prevent errors
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 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 |
관련 이슈
작업 내용
특이 사항
리뷰 요구사항 (선택)