Perforce p4 Command-Line Reference: Daily Commands, Changelists, Sync, and Merge Workflow

Originally published on 2010-05-13; fully revised and updated.

This guide is for DevOps engineers and developers who use the p4 command-line client with Perforce. It turns the original quick command list into a structured reference you can use in day-to-day work: opening files, managing changelists, syncing revisions, integrating branches, and submitting safely.

Source article: Most User P4 Command Line – P4 Commands Reference.

How the p4 workflow fits together

Most teams follow a repeatable lifecycle: authenticate, sync, open files for add/edit/delete, review changelist content, resolve conflicts if needed, then submit.

flowchart TD
    A[Check server and workspace] --> B[p4 login]
    B --> C[p4 sync]
    C --> D{Work needed}
    D -- New file --> E[p4 add]
    D -- Modify file --> F[p4 edit]
    D -- Remove file --> G[p4 delete]
    E --> H[p4 change review]
    F --> H
    G --> H
    H --> I[p4 resolve when needed]
    I --> J[p4 submit]
    J --> K[p4 have or p4 sync verify]

Core p4 commands at a glance

Command patterns you will use most

Add new files

Use p4 add to open files for addition. You can set file type, assign a changelist, or force-add a literal filename pattern.

p4 add -t binary file.pdf
p4 add -c 13 *
p4 add README ~/src/*.c
p4 add -f *.cCode language: JavaScript (javascript)

Edit, delete, and revert files

p4 edit -t text+k doc/*.txt
p4 delete //depot/README
p4 delete -c 40 file
p4 revert //depot/...

Manage changelists and submit

p4 change
p4 change -f 25
p4 changelists
p4 submit
p4 submit -c 41

Sync and inspect revision state

p4 sync
p4 sync file.c#4
p4 sync //depot/proj1/...@21
p4 haveCode language: PHP (php)

Integrate and resolve branch changes

p4 integ //depot/dev/... //depot/rel2/...
p4 resolve
p4 submitCode language: JavaScript (javascript)

Compare similar commands before you run them

User, authentication, and administration commands

These commands are commonly used during setup, troubleshooting, or admin workflows. Run administrative operations carefully, especially in shared environments.

p4 info
p4 login
p4 passwd
p4 user
p4 user joe
p4 user -d sammy
p4 admin stop

P4CONFIG for repeatable local setup

The original post mentions P4CONFIG. In practice, teams often use it to keep consistent local client settings. Keep secrets out of shared files and follow your organization policies.

export P4CONFIG=.p4config
p4 infoCode language: JavaScript (javascript)

P4PORT=perforce.example.com:1666
P4USER=your-user
P4CLIENT=your-workspace

Common pitfalls and best practices

• Open files with p4 add, p4 edit, or p4 delete before editing workflow-critical files.
• Prefer numbered changelists for multi-file work; avoid large, mixed default changelists.
• Sync before integrate and before submit to reduce avoidable conflict resolution.
• Use p4 have and p4 changelists to verify state before submit.
• Be careful with wildcard patterns like *.c; shell expansion behavior can differ by environment.
• Treat p4 admin stop as a controlled maintenance action, not a routine command.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.