如何在Perforce中对depot仓库执行Git式fork（复制到tasks/streams）？

Hey there! Let's walk through how to pull off that Git-style fork in Perforce—since the tool uses different terminology and workflows, it's easy to get confused at first. I'll cover two common scenarios based on whether your streams directory is a regular depot path or part of Perforce's modern Stream branching system.

Scenario 1: Forking a regular depot folder to a standard streams directory #

If //depot/streams/ is just a regular folder in your depot (not using Perforce Stream architecture), follow these steps to create a linked, fork-like copy (with history preserved for future merges):

• First, sync the source folder to your local workspace to ensure you have the latest version:

  p4 sync //depot/your-source-folder/...
  

• Next, create the target folder in the depot (skip this if it already exists):

  p4 mkdir //depot/streams/your-forked-folder
  p4 submit -d "Create target directory for forked project"
  

• The core "fork" step uses Perforce's integrate command, which establishes a branch relationship (similar to Git's fork with upstream tracking):

  p4 integrate //depot/your-source-folder/... //depot/streams/your-forked-folder/...
  

• Resolve any conflicts (if there are overlapping changes, though this is unlikely for a fresh fork):

  p4 resolve
  

• Finally, submit the forked copy to the depot:

  p4 submit -d "Fork source folder to streams directory"
  

Scenario 2: Forking into a Perforce Stream (modern branching model) #

If your streams directory is part of Perforce's Stream system (the recommended approach for scalable branching), the process is more streamlined:

• First, list existing streams to confirm your source stream or depot path:

  p4 streams
  

• Create a new Stream based on your source project. For example, a development type stream (ideal for forking to work on features):

  p4 stream -t development //depot/streams/your-forked-stream
  

  When prompted, edit the Stream configuration to set your source folder/stream as the Parent (this links the fork to the original for future merges).
• Switch your workspace to the new Stream and sync the files:

  p4 switch //depot/streams/your-forked-stream
  p4 sync
  

  That's it—you now have a fully functional fork tied to the original project, ready for independent development.

Quick note on "raw" file copies #

If you don't care about preserving branch history (not recommended for long-term development), you can use p4 copy instead of integrate:

p4 copy //depot/your-source-folder/... //depot/streams/your-forked-folder/...
p4 submit -d "Copy source folder to streams directory"

Just keep in mind this creates an unrelated copy, so merging changes back to the original will be much harder later.

Let me know if you hit snags with conflict resolution or Stream setup—I’m happy to help troubleshoot!

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