Add post-merge CI and build release workflows #185
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
After squashing and mergin a commit on top of what's on the main branch there can be merge issues. Add a post-merge (ie. push) trigger for the same workflows that are used for pull requests to help flag merge issues. For these workflows, it will be useful to upload the release artifacts in case someone would like to manually test it. In the future there is also a possibility of larger e2e test suites that could run on fresh Linux containers without existing swift toolchains. Add a new workflow to produce release artifacts for Linux on a manual workflow dispatch either from the GitHub UI, or via the REST interface.
shahmishal
approved these changes
Nov 13, 2024
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.
After squashing and merging a commit on top of what's on the main branch there can be merge issues. Add a post-merge (ie. push) trigger for the same workflows that are used for pull requests to help flag merge issues.
For these workflows, it will be useful to upload the release artifacts in case someone would like to manually test it. In the future there is also a possibility of larger e2e test suites that could run on fresh Linux containers without existing swift toolchains.
Add a new workflow to produce release artifacts for Linux on a manual workflow dispatch either from the GitHub UI, or via the REST interface.