ci(cross-app): skip workflows on kit-only changes#626
Conversation
cross-app-connect has no dependency on @vechain/vechain-kit, so kit-only changes can't break its build or affect what's deployed. Drop the packages/vechain-kit/** path filter from both the PR check and the Pages deploy so they only run when cross-app, yarn.lock, or the workflow file itself changes. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Size Change: 0 B Total Size: 8.84 MB ℹ️ View Unchanged
|
Summary
cross-app-connecthas no dependency on@vechain/vechain-kit(checkedcross-app-connect/package.json), so kit-only changes can't affect its build or what gets deployed.packages/vechain-kit/**from thepaths:filter of both the PR check and the Pages deploy workflows.mainthat only touches the kit no longer runs cross-app type-check/build or redeploys the Pages site.Path filters kept (still legit triggers):
cross-app-connect/**yarn.lock(shared lockfile — dep updates can still affect cross-app's build)Test plan
cross-app-connect/**→ check runs as beforemain→ no Pages deploycross-app-connect/**commit tomain→ Pages deploy runs🤖 Generated with Claude Code