Reconcile main history into staging - #113
Merged
Merged
Conversation
…ision-workflow ci: register staging-only component metadata repair workflow
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.
Outcome
Ensure staging contains all main history without changing current staging content.
Work authority
Contributor mode:
Plan
Merge main ancestry into current staging and preserve the exact staging tree.
Changes and commits
The merge joins production history into staging without restoring superseded content.
Verification
Risk and rollback
This is ancestry-only reconciliation. The prior staging commit remains the first parent and provides an exact rollback point.
Completion summary
Staging is no longer behind main and its file tree is unchanged.
Submission checklist