Add GitHub Actions job to deploy to NuGet#7117
Merged
Conversation
Contributor
Test Results 1 files ±0 1 suites ±0 1m 16s ⏱️ ±0s Results for commit 4b1a9e0. ± Comparison against base commit d40a398. This pull request removes 32 and adds 32 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Contributor
|
@bdukes I did setup Nuget for trusted publishing, we can discuss in todays meeting... |
37e1a98 to
c962041
Compare
c962041 to
4b1a9e0
Compare
mitchelsellers
approved these changes
Mar 18, 2026
Contributor
Author
|
It's ready, the version issue is only on the |
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
3 participants
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.
Summary
This PR adds a second job to the GitHub Actions workflow for CI. It only runs when the build is manually triggered, and it uses an environment to gate its running until approved. It's setup to use NuGet Trusted Publishing, which still needs to be setup on the NuGet side (currently configured to use
MitchelSellersas the NuGet user via an environment secret).Alternatives Considered
Instead of tacking this on to the end of each CI request, it could be a separate workflow that builds everything again (maybe triggered on creating a release), or a manual workflow that requires specifying an artifact ID.