Don't run Get Coverage step for fork PRs#158
Merged
nesono merged 1 commit intonesono:mainfrom Dec 23, 2025
Merged
Conversation
This is due to the limitations of the orgoro/coverage action when it comes to the permissions of the default GITHUB_TOKEN as described in orgoro/coverage#281 The effect is that there will not be any coverage information posted as a comment for fork PRs. I think this is an ok workaround to allow nesono#156 and nesono#154 to land for now
nesono
approved these changes
Dec 23, 2025
Owner
nesono
left a comment
nesono
left a comment
There was a problem hiding this comment.
Thanks, I was about to prepare the same PR 👍
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.
Hitting this in https://github.com/nesono/repo_structure/actions/runs/19702725589/job/58818637355:
This is due to the limitations of the orgoro/coverage action when it comes to the permissions of the default GITHUB_TOKEN as described in orgoro/coverage#281
The effect is that there will not be any coverage information posted as a comment for fork PRs.
I think this is an ok workaround to allow #156 and #154 to land for now