Repository navigation
feat: nightly follows the template's dev, and the release branches what master releases - #11
Merged
Merged
Conversation
…at master releases
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 template now works in
devand releases what reachesmaster(sawking-tech/DotNetSolutionKit, CONTRIBUTING):nightlyfollowsdev, where the next release is built;master's last commit instead of the latest GitHub release: whatever reachesmasteris a release. Whilemasteris not tagged yet (release.yml still publishing), they wait for the next check;Checked against the live repository: the tag lookup finds
v2.6.2on its commit and nothing on today'smaster(19094e9, not released), so the release branches stay on 2.6.2.🤖 Generated with Claude Code
https://claude.ai/code/session_01NczLWHuimhqeSmGQ2jjX8X