企业版与开源版同仓时，能否将私有仓指定文件夹镜像至公开仓库？

Absolutely, this is totally feasible! You can mirror just your folder-for-open-source-edition from your private monorepo to a public repo, while keeping your enterprise code secure and avoiding the headache of maintaining two disconnected repos manually. Here are two proven approaches:

Approach 1: Git Subtree Split + Automated CI/CD #

This method lets you split out the open-source folder into a dedicated branch, then push that branch to your public repo. You can automate the whole process so updates to your private monorepo automatically sync to the public repo.

1. First, split the open-source folder into a standalone branch in your private repo:

   git subtree split --prefix=folder-for-open-source-edition -b open-source-branch
   

2. Add your public repo as a remote to your private repo:

   git remote add public-repo git@your-public-host.com/your-org/open-source-repository-public.git
   

3. Push the split branch to the public repo's main branch:

   git push public-repo open-source-branch:main
   

4. Automate the sync with CI/CD:
   Set up a workflow (using GitHub Actions, GitLab CI, etc.) that triggers every time your private repo's main branch updates. The workflow will run the split and push commands above, so your public repo stays in sync automatically.

Approach 2: Git Filter-Repo (Modern Alternative to Filter-Branch) #

If you want a cleaner history (only commits related to the open-source folder), use git filter-repo—it's faster and more reliable than the old git filter-branch.

1. Clone your private repo to a temporary local directory:

   git clone git@your-private-host.com/your-org/main-repository-private.git temp-repo
   cd temp-repo
   

2. Filter the repo to only keep the open-source folder (and move its contents to the root):

   git filter-repo --path folder-for-open-source-edition --path-rename folder-for-open-source-edition/:./
   

3. Push the filtered repo to your public repo:

   git remote add public git@your-public-host.com/your-org/open-source-repository-public.git
   git push public main --force
   

   Like the first approach, you can automate this with CI/CD to keep the public repo updated whenever your private monorepo changes.

Handling Community Contributions #

When the community submits PRs or issues to your public repo, here's how you bring those changes back into your private monorepo:

• Merge the PR into the public repo's main branch first.
• Pull those changes into your private monorepo's folder-for-open-source-edition using:

  git subtree pull --prefix=folder-for-open-source-edition public-repo main --squash
  

This keeps your open-source folder in sync with community contributions without manual copy-pasting.

Key Notes to Keep in Mind #

• Permissions: Make sure your CI/CD workflow has access to both your private repo (via a deploy key or access token) and permission to push to the public repo.
• Sensitive Code: Double-check that your folder-for-open-source-edition doesn't contain any enterprise-only code or secrets before pushing to the public repo.
• History: Both methods preserve the commit history related to the open-source folder, so your community can see the project's evolution.

内容的提问来源于stack exchange，提问作者lolski