Point the workflow triggers at the actual default branch - #23
Merged
Merged
Conversation
The Build and Test workflow triggered on main, vNext and develop. This repository's default branch is master, and neither main nor develop exists, so the workflow never ran - not on pushes to master and not on pull requests targeting it. PR #22 merged with no checks for that reason. Both trigger blocks now list master and vNext. The publish workflow is unaffected by this, since a tag trigger is not branch-scoped, but its GitHub Release body linked to blob/main/CHANGELOG.md, which 404s on a master repository; that path is corrected too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
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.
What
Build and Testtriggered onmain,vNextanddevelop. This repository's defaultbranch is
master, and neithermainnordevelopexists on the remote — so theworkflow never ran, on pushes to
masteror on pull requests targeting it. PR #22 mergedwith no checks for that reason.
Both trigger blocks now list
masterandvNext.developis dropped rather thanrenamed; there is no such branch.
Also
publish-nuget.ymlis unaffected by the trigger bug — a tag trigger is not branch-scoped,so
on: push: tags: ['v*.*.*']fires regardless. But its GitHub Release body linked toblob/main/CHANGELOG.md, which 404s on amasterrepository. Corrected toblob/master/.Verification
Workflow YAML only; no source, project or package change. Merging this makes the PR itself
the first run of
Build and Teston this repository — see the checks below.