Repository navigation
Publish releases only from a manual release workflow - #1
Merged
Merged
Conversation
Builds on pushes and pull requests now only upload a workflow artifact. The new Release native MarkText workflow reuses the build and publishes its files to a release named after the MarkText tag.
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
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.
Splits releasing out of the build workflow.
build.ymlruns on pushes tomainand on pull requests and uploads the build as a workflow artifact only. It is also callable viaworkflow_call.release.yml(manualworkflow_dispatch, inputsmarktext-refandnativeboat-version) reuses the build and publishes the exe, a ZIP of the output folder andSHA256SUMS.txtto a release named after the MarkText tag.cancel-in-progressnow applies to pull requests only.