Repository navigation
feat: lifecycle - the life of a solution, from the release two minors back to dev, by dotskit - #21
Merged
Merged
Conversation
… back to dev, by dotskit - .samples/lifecycle.sh: a solution made with the template alone at the last patch of the minor two below dev's version on nuget.org, a team's change, then dotskit init, upgrade, new (a service), new (a flag of a service it has) and new --force, a commit each; dotskit builds after each; the team's line must be there at the end - .github/workflows/lifecycle.yml: builds the branch lifecycle again when the template's dev has moved, keeps its reports, pushes with the deploy key so its CI runs - generate.sh: runs manual-add-projects.sh only where the template still ships it (before 2.8), and carries the lifecycle automation on the default branch
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
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.
A branch
lifecycleshows the life of a solution, and is a condition of releasing the template (CONTRIBUTING of DotNetSolutionKit, Releases)..samples/lifecycle.sh: a solution made with the template alone at the last patch of the second minor below dev's version among the releases on nuget.org (2.6.2 for 2.8), a team's change, then dotskit init, upgrade, new (a service), new (a flag of a service it has) and new --force, a commit each; dotskit builds after each; the team's line must be there at the end. dotskit and the template it upgrades to are dev's sources, so the run checks the next release before it is out..github/workflows/lifecycle.yml: builds the branch again when dev has moved (daily, and by hand), keeps its reports, pushes with the deploy key so its CI runs; one run at a time.generate.sh: runs manual-add-projects.sh only where a release still ships it (before 2.8), and carries the lifecycle automation on this default branch.Proven on runners before the PR, on a temp branch into
tmp-lifecycle: a branch from nothing (its CI green, its report written), and a rebuild over a branch with reports (reports kept, CI started again). The livelifecycle(from a local run of the script) has a green CI.Reviewed before the PR by an agent without context, three rounds, closed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Vefp3uznXHA37YYMCkUouw