Repository navigation
chore: migrate source history to edgepillar - #206
Closed
edgepillar wants to merge 1 commit into
Closed
edgepillar wants to merge 1 commit into
edgepillar wants to merge 1 commit into
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
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.
Prepare the requested source-history attribution change to
edgepillarfor both author and committer, using the account-provided GitHub no-reply identity. The replacement source DAG preserves every original file tree, commit message, timestamp and parent order. Original objects, reports and the complete SHA map remain retained separately. Platform-generated test merge objects are historical evidence.The rewritten historical tip is
fa7b2a7c9241e03fbb4b9f328bcdd4909961cdcd. This draft compares one separate policy commit against that tip. OnlyAGENTS.mdandCONTRIBUTING.mdchange content, documenting future attribution, local identity guards, local merge creation and revision-bound verification. Protocol code and fixtures are unchanged.Fresh local validation: all 4,471 offline cases in four complete partitions passed, with no skips or resource warnings; artifact checks passed for all 2,498 index/worktree file versions. Four positive and nine refusal controls exercised the installed pre-commit/pre-push identity guards. Earlier native outputs remain byte-bound references for unchanged code, not fresh execution of this revision.
This preview creates two new refs and does not replace the current main or original branch heads. Fresh hosted checks and original-artifact acceptance for this exact head are required before the authorized history replacement. A main update has a separate push-triggered CI acceptance gate. Do not reuse an earlier CI run or frozen assessment as qualification of a replacement SHA. Application/core remain NO-GO; recovery action remains NONE and independent assessment remains unfilled.
Original main source commit map (content-preserving history only)