Maintainers can use publish.cmd, Nuke will ask for a nuget key and a github key and it will publish a new release based on release_notes.md as requested on discord.
There's also the option to do the same without publishing, good for testing the package locally: .\build.cmd --target pack --configuration release
Artifacts are produced in the artifacts folder, already gitignored.
I've left some todo comments for a future CI possibility.
Maintainers can use
publish.cmd, Nuke will ask for a nuget key and a github key and it will publish a new release based on release_notes.md as requested on discord.There's also the option to do the same without publishing, good for testing the package locally:
.\build.cmd --target pack --configuration releaseArtifacts are produced in the
artifactsfolder, already gitignored. I've left some todo comments for a future CI possibility.