(GH-77) Push to gallery on new tags #78
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
Instead of pushing on merges to master, push to the PowerShell gallery on new tags being added. We want to use tagging for versioning and getting to version history in the repository, so it's good to just set that up appropriately.
|
Probably best to review the second commit as it removes the noise. |
lawrencegripper
approved these changes
Apr 20, 2017
|
@lawrencegripper tags aren't unique to a branch - they point to a particular commit with a specified history. While we usually tag off master, it's not a requirement. For example, if you have a security fix that you want to publish for a previous major version, you might end up with a new tag not off master. |
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.
Instead of pushing on merges to master, push to the PowerShell gallery
on new tags being added. We want to use tagging for versioning and
getting to version history in the repository, so it's good to just set
that up appropriately.
Closes #77