Modify pre-release action#492
Merged
renkun-ken merged 1 commit intoREditorSupport:masterfrom Dec 10, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fix #484
This action modifies the pre-release-action by updating the last pre-release instead of creating a new one, which avoids notifying subscribers about a new release after each push to master.
Notifications about proper releases are not affected.
I tested this in a private repository and it seems to work nicely. The first pre-release using this action might trigger the notification or need some cleanup, but subsequent pre-releases should be fine.
To test: clone some vscode-extension to a private repo and push to master a couple of times.