cleanup: remove accidentally-nested amplifier-app-cli/ directory from PR #158#165
Merged
cleanup: remove accidentally-nested amplifier-app-cli/ directory from PR #158#165
Conversation
PR #158 (merge commit ca9362d, with earlier commit 8944aec) accidentally committed a full copy of the repo at amplifier-app-cli/ inside the repo root — TWO levels of self-nesting, 340 stale files. This is the mirror of the amplifier-foundation cleanup (PR #174). Root cause: sub-agents used relative paths prefixed with the submodule name (e.g., 'amplifier-app-cli/amplifier_app_cli/main.py') while cwd was already inside the submodule, creating the nested tree. Verified no legit content at risk: - pyproject.toml IDENTICAL between root and both nested copies - uv.lock IDENTICAL between root and both nested copies - Root source has refactored ui/dashboard_renderer.py which does NOT exist in nested copies — nested snapshots are older, superseded state - Root main.py is the current refactored version Also adds /amplifier-app-cli/ to .gitignore as a recurrence guard. 4 stale Dependabot PRs (#159, #160, #161, #162 — all targeting nested /amplifier-app-cli paths) will be closed as no longer applicable.
This was referenced Apr 20, 2026
Closed
Closed
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 #158 (merge commit
ca9362d, with earlier commit8944aec) accidentally committed a full nested copy of the repo atamplifier-app-cli/inside the repo root. Two levels of self-nesting, 340 stale files. This is the mirror of the amplifier-foundation cleanup (microsoft/amplifier-foundation#174).Root cause
During a multi-agent development session, sub-agents used relative paths prefixed with the submodule name (e.g.,
amplifier-app-cli/amplifier_app_cli/main.py) while their cwd was already inside the submodule, creating nested paths likeamplifier-app-cli/amplifier-app-cli/amplifier_app_cli/main.py.Verification (nothing legit at risk)
pyproject.tomlis identical between root and both nested copiesuv.lockis identical between root and both nested copiesui/dashboard_renderer.py— this file does not exist in the nested copies, confirming nested snapshots are older, superseded statemain.pyis the current refactored version; nested copies have the pre-refactor inline implementationChanges
git rm -rf amplifier-app-cli/— removes the entire nested tree (both levels, 340 files)/amplifier-app-cli/to .gitignore to prevent recurrenceFollow-up
Closing these 4 stale Dependabot PRs (targeting nested paths that will not exist after merge): #159, #160, #161, #162.
The /config command feature from PR #158 is unaffected — this is pure cleanup of collateral pollution.