Replace NUKE build with plain dotnet CLI workflows - #46
Merged
Conversation
The NUKE build only wrapped five dotnet CLI calls (restore, format, build, pack, push) with no tests, matrix, or platform-specific logic, so the build project, bootstrapper scripts and .nuke folder were more indirection than the project needed. CI changes previously required editing C# attributes and regenerating the workflow YAML. The two workflows are now hand-written and call dotnet directly. Versioning is unaffected: Nerdbank.GitVersioning is referenced by the library project, not by the build.
danielchalmers
force-pushed
the
remove-nuke
branch
from
July 27, 2026 03:00
dd1f828 to
d6107cb
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.
The NUKE build wrapped five
dotnetCLI calls — restore, format, build, pack, push — with no tests, no build matrix, and no platform-specific logic. In exchange it cost an extra project (build/_build.csprojplus itsNuke.Commondependency), the.nukefolder, three bootstrapper scripts, and a layer of indirection: changing CI meant editing C# attributes inBuild.csand regenerating the workflow YAML rather than editing the YAML directly.Changes
build/,.nuke/,build.cmd,build.ps1,build.sh, and removed_build.csprojfrom the solution.dotnetdirectly, preserving the existing behaviour:dotnet format whitespace/style --verify-no-changes, build, pack, upload packages artifact.--skip-duplicate, upload packages artifact.permissions:block to the release job (packages: write) so the GitHub Packages push does not depend on the repository's default token permissions.global.jsonorDirectory.Packages.props, neither of which exists in this repo, and now has arestore-keysfallback.