Merge strategy for integration workflow#219
Merged
Merged
Conversation
69 tasks
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.
Changes the way the
integrationbranch gets updated. Previously this workflow would take the latest frommain, apply schema and Cargo updates, and then force push those changes tointegration. This change instead now mergesmainintointegration(and specifically uses the generated code frommainin the case of conflicts) as the first step. Updates are then applied over top of the merged branch.There is a chance for this action to fail if there are conflicts in non-generated files and those would need to be manually resolved.