Automatically push the Windows installer to the main branch #35
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
Previously, it had to be manually generated and pushed to the repo at each new pull request merge.
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.
In #27, a GitHub workflow was added in order to automate the build and test of the Windows installer distributed with MyoFInDer. The installer was then made available to admins through a workflow artifact. However, a manual step was still required in order to push the newly built installer to the repository.
With this PR, the GitHub workflow is modified so that it automatically builds, tests, and pushes the newly built installer to the main branch. The push is performed each time a pull request is merged into the main branch, or a commit is directly pushed to the main branch.