Repository navigation
Preserve integrated feature commit lineage; staging tree unchanged - #31
Merged
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
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.
Refs #30; central treeseed-ai/platform#626.
User-requested cleanup preserving original commits and full lineage. Native git cherry on each exact listed feature head (Issue body) found zero new patches; all have integrated equivalents in protected staging. This Git ours history-only merge records those original commits as ancestors without reapplying outdated branch trees.
Initial staging
452bf0945520dcd0db9ac3f39fb16626b1047fe6; candidated48f85c80ddde5184eb8c65ac5f0810c566a9ea6; EXACT unchanged Git tree38873537c72c72359c537c6123bd28c7e86ef6a0. Every retained feature head verified ancestor of candidate. No source, tests, config, workflow, dependencies, policies, release tags, runtime or activation changes. Fresh required Actions must pass before protected staging merge. Then redundant refs can be removed recoverably from protected history, followed by verified staging-to-main promotion.