Skip pytest coverage comment on fork PRs - #223
Merged
Merged
Conversation
This was referenced Aug 22, 2026
Closed
Merged
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
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.
Summary
GITHUB_TOKENregardless of the job'spermissions: pull-requests: write, so thePytest coverage commentstep fails with Resource not accessible by integration and marks the wholebuildjob red even when every test passes (e.g. fix: lazy + crash-safe epoch formatting in eclipse-check debug log #215: 38 passed, 0 failures, 91% coverage, job still red).pull_request_targetinstead, but that runs fork code with a writable token — not a trade worth making for a coverage comment.Related to #215, #222
Test plan
Pytest coverage commentstep still runs and posts the Coverage Report comment.buildgoes green.