Block Release Publishing workflow from automatically running on forks#1450
Merged
jeffhandley merged 1 commit intomodelcontextprotocol:mainfrom Apr 3, 2026
Conversation
Add an if condition to the build-all-configs job to prevent the Release Publishing workflow from running on forks via schedule or release triggers. The workflow_dispatch trigger is exempted so fork owners can still manually test the workflow. Since all downstream jobs (build-package, publish-github, publish-release, publish-nuget) depend on build-all-configs via the needs chain, they are automatically skipped when build-all-configs is skipped. This is consistent with the existing repository check in the publish-nuget job and docs.yml workflow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
I just realized my fork was using 6.5 GB of actions storage from this workflow. |
eiriktsarpalis
approved these changes
Mar 23, 2026
jeffhandley
added a commit
to jeffhandley/modelcontextprotocol-csharp-sdk
that referenced
this pull request
Apr 3, 2026
…modelcontextprotocol#1450) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Add an if condition to the build-all-configs job to prevent the Release Publishing workflow from running on forks via schedule or release triggers. The
workflow_dispatchtrigger is exempted so fork owners can still manually test the workflow.Since all downstream jobs (build-package, publish-github, publish-release, publish-nuget) depend on build-all-configs via the needs chain, they are automatically skipped when build-all-configs is skipped. This is consistent with the existing repository check in the publish-nuget job and docs.yml workflow.