apply-change-to-repo-hierarchy

To apply coordinated changes across a git repository and submodules, you provide a repository path, change prompt, and branch name. The automation discovers submodules, filters third-party repos, and applies dependency-aware changes leaf-to-root with topic-branch isolation.

Dependency-aware sequencing updates git submodules by applying changes leaf-to-root. This ensures upstream dependencies are modified before parent repositories, maintaining consistency and reducing manual drift across the entire repository hierarchy.

Yes, you can automatically build and test repositories before creating pull requests. After applying changes across the hierarchy, the workflow validates repository quality, verifies traceability, and outputs modified repos and PR references.

Yes, the workflow filters third-party repositories during the submodule discovery phase. This ensures that automated changes are only applied to your own codebase, preventing accidental modifications to external dependencies.

To start automating changes across your repository hierarchy, you need a starting repository path, a change prompt describing the modifications, and a topic branch name. The workflow clones to a temporary work area to safely apply the changes.

The best way to isolate feature changes across nested repositories is using topic-branch isolation. This approach clones the hierarchy to a temporary work area and applies context-aware prompts leaf-to-root, ensuring consistent branch tracking.