fix sourcify_all_chains permissions#1845
Merged
Merged
Conversation
Child workflow succeeds on its own, but requires permissions to be passed explicitly when invoked from parent workflow. [Failed build example](https://github.com/NomicFoundation/slang/actions/runs/27197438935): > The nested job 'singleShard' is requesting 'contents: read', but is only allowed 'contents: none'.
|
Contributor
|
Bencher Report| Branch | OmarTawfik/fix-sourcify-permissions |
| Testbed | ci |
⚠️ WARNING: Truncated view!The full continuous benchmarking report exceeds the maximum length allowed on this platform.
🐰 View full continuous benchmarking report in Bencher
⚠️ WARNING: No Threshold found!Without a Threshold, no Alerts will ever be generated.
nebasuke
approved these changes
Jun 9, 2026
Member
|
Thanks for the fix! |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Child workflow succeeds on its own, but requires permissions to be passed explicitly when invoked from parent workflow.