Skip NuGet publish steps for fork PRs in CI#1063
Merged
Conversation
Fork PRs don't have access to secrets or OIDC authentication, causing the deploy job to fail. Add conditions to skip the NuGet login and publish steps when the PR comes from a fork, while keeping the deploy job itself green. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Mar 28, 2026
Closed
Closed
This was referenced Apr 11, 2026
Closed
This was referenced Apr 18, 2026
Open
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
1 participant
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
deployjob in CI requires OIDC authentication (NuGet/login) and secrets (FEEDZ_APIKEY) to publish NuGet packages. Fork PRs don't have access to either, causing the job to fail. Sincedeployis a required check, this blocks merging any fork contribution.This adds a condition to the NuGet login and publish steps so they are skipped when the PR comes from a fork, while the
deployjob itself still runs and succeeds. The condition used is:This ensures publishing runs for pushes to
main, workflow dispatches, and same-repo PRs — but is safely skipped for fork PRs.