Publishing dotnet-client to nuget.org on release #279
Merged
Conversation
This file contains 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
Now when a release tag is generated publish our dotnet client to nuget.org - This is to make it more easily accessible to people wanting to use it Also the dotnet client no longer is generated on dotnet build Instead it is generated as part of running the proto.sh, to make sure it stays in sync with when the swagger gets updated
jankaspar
approved these changes
Dec 10, 2019
svc-gh-ghzonetrans-p
pushed a commit
that referenced
this pull request
Nov 13, 2024
…trics (#279) * Setting available capacity for cordoned clusters to 0 in scheduler metrics * Setting default values for keys under schedulableNodeCountByCluster in scheduler metrics * Removing dead code path
MustafaI
added a commit
that referenced
this pull request
Nov 13, 2024
…trics (#279) (#4044) * Setting available capacity for cordoned clusters to 0 in scheduler metrics * Setting default values for keys under schedulableNodeCountByCluster in scheduler metrics * Removing dead code path Co-authored-by: Mustafa Ilyas <[email protected]>
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.
Now when a release tag is generated publish our dotnet client to nuget.org
Also the dotnet client no longer is generated on dotnet build
Instead it is generated as part of running the proto.sh, to make sure it stays in sync with when the swagger gets updated