chore: added nuget.org release workflow #1191
Merged
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
ghuntley
force-pushed
the
release-workflow
branch
from
dfcbaf3 to
ecd0a65
Compare
ghuntley
changed the title
ghuntley
force-pushed
the
release-workflow
branch
9 times, most recently
from
4708231 to
a09f639
Compare
ghuntley
force-pushed
the
release-workflow
branch
from
a09f639 to
ba31be1
Compare
glennawatson
pushed a commit
that referenced
this pull request
Mar 23, 2019
* wip * here goes 7 minutes of my life * Revert "here goes 7 minutes of my life" This reverts commit cc34607. * appveyor plz * add this in until we release, then remove * this should be it
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore
What is the current behavior? (You can also link to an open issue here)
CI only publishes to MyGet.org
What is the new behavior (if this is a feature change)?
developbranch to MyGet.orgmasterbranch to NuGet.org when the branch is tagged (trigger by clicking "publish release" in GitHub UI)Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements
Other information: