-
Notifications
You must be signed in to change notification settings - Fork 616
Fix CLA issues in workflows #6108
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
Release note changesNo release note changes were detected. If you made changes that should be |
Unit Test Results 954 files + 950 954 suites +950 34m 46s ⏱️ + 34m 43s For more details on these failures, see this check. Results for commit 7469445. ± Comparison against base commit 3dc208c. ♻️ This comment has been updated with latest results. |
Size Report 1Affected ProductsNo changes between base commit (050cc89) and merge commit (5d88991).Test Logs |
Coverage Report 1Affected Products
Test Logs |
Per b/353295303,
This updates our
post_release_cleanup
workflow to use thegoogle-oss-bot
as the signee. This should allow the workflow to pass CLA, asgithub-actions
is not supported.Note that while
create_release
does create a PR that could take advantage of this, we've chosen to keep it in a state where the CLA fails; such that the PR is not accidentally merged (as that PR should not be merged).