ci(fork): add fork release publisher to the default branch#4
Open
cliedeman wants to merge 1 commit into
Open
Conversation
Place release-fork.yml on main so the "Run workflow" button appears in the Actions UI (workflow_dispatch is only surfaced from the default branch). When dispatching, select the release/fork-<version> branch - main has no fork package changes, so it must not be published from. This is the only fork commit on main, which otherwise mirrors upstream; preserve it (or re-add) when syncing main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cliedeman
force-pushed
the
ci/release-fork-on-main
branch
from
June 26, 2026 22:03
65e9ac1 to
45b806c
Compare
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.
Adds
.github/workflows/release-fork.ymltomainso the Run workflow button appears in the Actions UI —workflow_dispatchis only surfaced from the repo's default branch.This is the same workflow already on
fork/release/fork-16.3.0(packs + pushes onlyStackworx.StrawberryShake.{Razor,Blazor,Tools}via NuGet trusted publishing). It's the only fork commit onmain, which otherwise mirrors upstream.Usage
release/fork-16.3.0branch (or whichever release branch you're publishing).mainhas no fork package changes, so do not publish frommain.fork-*tag trigger also works directly on the release branch.Note
Keep (or re-add) this commit when syncing
mainfrom upstream, sincemainis otherwise a clean upstream mirror.🤖 Generated with Claude Code