Repository navigation
Grant CLA workflow the permissions it needs - #657
Merged
Merged
Conversation
Contributor
Test Results 8 files ±0 8 suites ±0 4m 9s ⏱️ -3s Results for commit c5fcc4c. ± Comparison against base commit fb9014a. This pull request removes 1 test.♻️ This comment has been updated with latest results. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The shared CLA workflow (
restatedev/restate/.github/workflows/cla.yml) needsactions,pull-requestsandstatuseswrite access. A reusable workflow can't get more permissions than its caller, so with the org'sGITHUB_TOKENdefault now read-only, this caller has to grant them explicitly. Otherwise the CLA run fails before it starts.Related: restatedev/restate#5697
🤖 Generated with Claude Code