Separate vsix build and deploy steps #32
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
- it was added to see if publish steps reads pat and can deploy - keeping them there will hide errors if we forgot to bump versions, thus remove
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.
We separate vsix build, publish-to-VS marketplace and publish-to-OpenVSX into 3 jobs, so that we can just rerun failed jobs if we forgot to update any of the outdated tokens.
Example:
https://github.com/MrOrz/vscode-gettext/actions/runs/7683610495
Note: the example is created with
skipDuplicate: true. In this PR, I removedskipDuplicate: truebecause it may hide errors if we forgot to bump versions.