cleanup: remove accidentally-nested amplifier-foundation/ directory from PR #160#174
Merged
Merged
Conversation
PR #160 (merge commit b10b8e7) accidentally committed a full copy of the repo at amplifier-foundation/ inside the repo root — two levels of self-nesting, 610 stale files. Verified no legit content at risk: - pyproject.toml IDENTICAL between root and nested copies - uv.lock IDENTICAL between root and nested copies - Nested configurator snapshots are older dev states (monolithic), not newer; the refactored package at amplifier_foundation/ (root) is current Also adds /amplifier-foundation/ to .gitignore to prevent recurrence from accidentally cloning the repo into its own working tree. 10 stale Dependabot PRs (#161, #162, #163, #164, #165, #166, #167, #168, #169, #170 — all targeting /amplifier-foundation paths) will be closed as no longer applicable.
This was referenced Apr 20, 2026
Closed
Closed
Closed
5 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.
Problem
PR #160 (merge commit
b10b8e73) accidentally committed a full nested copy of the repo atamplifier-foundation/inside the repo root. Two levels of self-nesting, 610 stale files. Dependabot has been generating PRs against files inside the nested paths since.Verification (nothing legit at risk)
pyproject.tomlis identical between root and nested copiesuv.lockis identical between root and nested copiesamplifier_foundation/configurator/__init__.pysnapshots are the older monolithic (643 and 673 line) dev versions; the refactored package at the root (231-line facade + _state_manager + _inspector + _provenance_utils) is current and unaffectedChanges
git rm -rf amplifier-foundation/— removes the entire nested tree/amplifier-foundation/to .gitignore to prevent recurrenceFollow-up
Closing these stale Dependabot PRs (targeting nested paths that will not exist after merge): #161, #162, #163, #164, #165, #166, #167, #168, #169, #170.
Keeping the 5 Dependabot PRs that target real root paths (#139, #141, #142, #156, #157 — for /modules/hooks-process-guard and root).
The SessionConfigurator feature itself from PR #160 is unaffected — this is pure cleanup of collateral pollution.