fix(cleanup): remove affinescript-vite/affinescriptiser self-clone accidents#669
Merged
Merged
Conversation
…cidents Both subdirectories were exact, fully-synced nested clones of this repo itself (identical HEAD SHA to affinescript's own tip, same origin remote, zero unique commits, zero uncommitted changes) -- structurally the same accidental-nested-clone class found and fixed in idaptik/idaptik today. No unique content: verified via diff and git log against the real tree before removal. Bundled to ~/developer/archive/affinescript-self-clone-cleanup-2026-07-01/ for recovery.
|
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.



Both
affinescript-vite/andaffinescriptiser/were exact, fully-synced nested clones of this repo itself — identical HEAD SHA to affinescript's own tip, same origin remote, zero unique commits, zero uncommitted changes. Same structural class as theidaptik/idaptikself-clone accident found and fixed today elsewhere in the estate. Verified no unique content before removal (diff + git log against the real tree); bundled both for recovery.