git-p4

git p4 command [options]

git p4 enables bidirectional interaction between Git and Perforce. It can import Perforce depot history into a Git repository and submit Git commits back to Perforce, supporting both migration and ongoing hybrid workflows.The tool maps Perforce depot paths to Git branches, allowing teams to work with Git locally while maintaining synchronization with a Perforce server. It supports gradual migration from Perforce to Git as well as permanent dual-system setups.The clone command creates a new Git repo from Perforce. sync fetches new changes without modifying working files. rebase syncs and rebases the current branch. submit sends Git commits to Perforce as individual changelists.

clone DEPOT

Import from Perforce depot.

Fetch changes from Perforce.

Submit git commits to Perforce.

Rebase on Perforce changes.

Target branch.

Auto-detect Perforce branch mappings.

Perform a bare clone (no working directory).

Use the Perforce client spec for file filtering.

Upstream location from which commits are identified to submit (default: most recent p4 commit reachable from HEAD).

Create shelved changelists instead of submitting.

Conflict handling during submit (default: ask).

Provide more detailed output.

Display help information.

Requires Python and p4 client. Some Perforce features don't map to git. Complex branch layouts challenging.

git p4 was created to support teams transitioning from Perforce to Git, or needing to work with both systems simultaneously.

git(1), p4(1), git-log(1)