ci: skip the release job on pull requests from forks - #637
Open
alkaz-nodemaven wants to merge 1 commit into
Open
alkaz-nodemaven wants to merge 1 commit into
alkaz-nodemaven wants to merge 1 commit into
Conversation
alkaz-nodemaven
had a problem deploying
to
MuslLinux
October 5, 2026 20:38 — with
GitHub Actions
Error
alkaz-nodemaven
had a problem deploying
to
MuslLinux
October 5, 2026 20:38 — with
GitHub Actions
Error
alkaz-nodemaven
had a problem deploying
to
MuslLinux
October 5, 2026 20:38 — with
GitHub Actions
Error
alkaz-nodemaven
had a problem deploying
to
MuslLinux
October 5, 2026 20:38 — with
GitHub Actions
Error
alkaz-nodemaven
had a problem deploying
to
MuslLinux
October 5, 2026 20:38 — with
GitHub Actions
Error
This branch was successfully deployed
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.
The
Releasejob fails on every pull request from a fork, atGenerate artifact attestation:Fork PRs get a read-only
GITHUB_TOKENand no OIDC token, whatever the jobdeclares, so that step can't pass there. It happened on #614 and on
https://github.com/0x676e67/wreq-python/actions/runs/36418255220, both with the
rest of the build green, so an outside contributor sees a red check they can't
fix.
This adds a job-level
if: the job still runs on tag pushes and on pullrequests from branches in this repository, including the attestation and the
uv publish --dry-run, and is skipped on fork PRs. Publishing is unchanged.