-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize auto approval workflow #5328
Conversation
ping @germa89 (Edit: Sorry to ping you a lot.) |
I may go spin this up in a dummy repo to test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
with: | ||
review-message: ":white_check_mark: Approving this PR because [${{ github.event.comment.user.login }}](https://github.com/${{ github.event.comment.user.login }}) said so in [here](${{ github.event.comment.html_url }}) :grimacing:" | ||
review-message: ":white_check_mark: Approving this PR because [${{ github.event.comment.user.login }}](https://github.com/${{ github.event.comment.user.login }}) said so in [here](${{ github.event.comment.html_url }}) :shipit:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know about it.
On GitHub, what is the significance of the "Ship It" squirrel?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5328 +/- ##
=======================================
Coverage 96.20% 96.20%
=======================================
Files 134 134
Lines 22717 22717
=======================================
Hits 21855 21855
Misses 862 862 |
I'm not totally sure if this will fix things, but I'm hoping that by moving the condtional from a workflow step to the job level, GitHub Actions will be able to parse whether or not it needs to spin up a runner or not.
At present, this workflow is eating up a ton of our CI bandwidth as it is spinning up a runner for every single PR comment and every time a comment is edited.
I went a step further and turned off runs for comment edits.