-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use a different GitHub Actions action for the PR size-labeler workflow #7219
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
Conversation
The previous labeler was buggy and poorly written.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7219 +/- ##
=======================================
Coverage 98.14% 98.14%
=======================================
Files 1104 1104
Lines 96352 96352
=======================================
Hits 94569 94569
Misses 1783 1783 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 assuming permissions will start working when this is merged.
PS: Please see the inline suggestion.
Co-authored-by: Pavol Juhas <[email protected]>
4ad7ce3
to
c758f16
Compare
Thanks for the excellent suggested chanages. I still don't know if the workflow permissions will work after merging. There is a restriction with token permissions in PRs from forks, so the current failures may be due to that. Unfortunately, if there's still a different permission problem, it's being masked by this failure and we won't know until the workflow is on the main branch. (I guess the right way to do it would have been to use a branch in the Cirq repo itself, instead of in a fork.) |
There is no way to get the error messages from the labeler action. We need to get the output if we want to note that something failed without failing the whole workflow. Thankfully, the action can be invoked more directly using `podman`, and it's not hard to revise the workflow to capture the output and write it as an annotation on the summary page.
f04262e
to
c213bd5
Compare
* Use a different action for size labeler GHA The previous labeler was buggy and poorly written. * Need set permissions for id-token * Update .github/pr-size-labels.yaml Co-authored-by: Pavol Juhas <[email protected]> * Widen the scope of excluded package-lock.json files * Improve explanation of how the settings work * Don't fail the workflow if labeling fails * Invoke the labeler program directly There is no way to get the error messages from the labeler action. We need to get the output if we want to note that something failed without failing the whole workflow. Thankfully, the action can be invoked more directly using `podman`, and it's not hard to revise the workflow to capture the output and write it as an annotation on the summary page. * Clarify comments some more --------- Co-authored-by: Pavol Juhas <[email protected]>
The previous GitHub Actions used as the labeling action was buggy. Switching to a different action that looks more promising.