> How do we not break all the merge commits that link a project specific PR? You won’t lose commits that are already made. Open PRs might become a problem, I’d

> How do we not break all the merge commits that link a project specific PR? You won’t lose commits that are already made. Open PRs might become a problem, I’d reopen them in the monorepo; this could be automated. You would lose meaningful inter-linking for commits, PRs and issues, since they all have the same overlapping #xxx namespace. You could triage all issues to the new monorepo, but the tool for rewriting history to re-reference issues (in the monorepo) and PRs (with the to-be archived repo as prefix) does not, as far as I know, exist. But it’s doable with some scripting and the GitHub API. git filter-repo (not filter-branch) is wonderful for all the merging of repos, moving/splitting into subdirectories without git mv. > What if you also are trying to manage external deps too? I’d go with git sub-repo for that.