Allow manual Emerge build uploads - #479
Open
michele-theleftbit wants to merge 1 commit into
Open
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
1 participant
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.
Why
The Emerge baseline build for commit
9ab5b88was not uploaded because the CI build failed while resolving remote Swift package dependencies.As a result, the XCFramework artifact was not generated and the Emerge upload step did not run. The following build could therefore not be compared against that commit.
A new push will likely resolve this automatically because Emerge can compare it against the latest successfully uploaded build.
What changes
Adds
workflow_dispatchto the Emerge workflow.This provides a manual fallback for transient CI or dependency-resolution failures, allowing us to upload a build without requiring a new code change and restore Emerge comparisons more quickly.
Validation