build: push nuget package to github registry #2
Conversation
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
|
@dosymep care to take a look at this? 4 eyes are better than 2 😉 I've added the constraint to package and push the package only on pyrevit-main and pyrevit-5-main, and skip the duplicates so that the ci doesn't errors out if we try to push a package with the same version. |
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.
I've messed up with my remotes and pushed directly in this repo, but that turned out to be a good thing since I already tested that the CI works!
You can see the package in the Packages section of the organization
Should we constrain the upload to specific branches? pyrevit-main? pyrevit-5-main?