Conversation
chore: remove obsolete deploy workflow for authentication service
|
Warning Rate limit exceeded@RandithaK has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 25 seconds before requesting another review. ⌛ 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. 📒 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 |
There was a problem hiding this comment.
Pull Request Overview
This PR removes the old deploy.yaml workflow file that was using a direct kubectl deployment approach. Based on the repository context, this workflow has been replaced by update-manifest.yaml which implements a GitOps pattern with ArgoCD. The file being deleted here appears to have already been renamed to deploy.yaml.old in the repository, indicating this is a cleanup operation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…ness on GH runners
fix: update image tag handling in update-manifest workflow for robust…
No description provided.