{"id":255,"date":"2026-10-13T03:41:20","date_gmt":"2026-10-13T03:41:20","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/05\/13\/most-user-p4-command-line\/"},"modified":"2026-10-13T03:41:21","modified_gmt":"2026-10-13T03:41:21","slug":"most-user-p4-command-line","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/most-user-p4-command-line\/","title":{"rendered":"Perforce p4 Command-Line Reference: Daily Commands, Changelists, Sync, and Merge Workflow"},"content":{"rendered":"\n

Originally published on 2010-05-13; fully revised and updated.<\/em><\/p>\n\n\n\n

This guide is for DevOps engineers and developers who use the p4<\/strong> 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.<\/p>\n\n\n\n

Source article: Most User P4 Command Line \u2013 P4 Commands Reference<\/a>.<\/p>\n\n\n\n

\"p4<\/figure>\n\n\n\n

How the p4 workflow fits together<\/h2>\n\n\n\n

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

\nflowchart TD\n    A[Check server and workspace] --> B[p4 login]\n    B --> C[p4 sync]\n    C --> D{Work needed}\n    D -- New file --> E[p4 add]\n    D -- Modify file --> F[p4 edit]\n    D -- Remove file --> G[p4 delete]\n    E --> H[p4 change review]\n    F --> H\n    G --> H\n    H --> I[p4 resolve when needed]\n    I --> J[p4 submit]\n    J --> K[p4 have or p4 sync verify]\n<\/pre>\n\n\n\n
Core p4 commands at a glance<\/h2>\n\n\n\n
Command<\/th>Primary purpose<\/th>Example<\/th>Practical note<\/th><\/tr><\/thead>
p4 add<\/td>Open new file(s) for addition<\/td>p4 add -t binary file.pdf<\/td>Can override typemap with -t<\/code>.<\/td><\/tr>
p4 edit<\/td>Open existing file(s) for edit<\/td>p4 edit -t text+k doc\/*.txt<\/td>File is checked out in workspace metadata.<\/td><\/tr>
p4 delete<\/td>Open file(s) for deletion<\/td>p4 delete \/\/depot\/README<\/td>Workspace file is removed immediately; depot changes on submit.<\/td><\/tr>
p4 revert<\/td>Discard pending file changes<\/td>p4 revert \/\/depot\/…<\/td>Returns open files to pre-opened state.<\/td><\/tr>
p4 change<\/td>Create or edit changelist spec<\/td>p4 change<\/td>Use numbered changelists for better control.<\/td><\/tr>
p4 changelists<\/td>List pending\/submitted changelists<\/td>p4 changelists<\/td>Useful before submit or cleanup.<\/td><\/tr>
p4 submit<\/td>Send open file revisions to depot<\/td>p4 submit -c 41<\/td>Final depot update happens here.<\/td><\/tr>
p4 sync<\/td>Copy depot files to workspace<\/td>p4 sync \/\/depot\/proj1\/…@21<\/td>Supports revision and changelist targets.<\/td><\/tr>
p4 have<\/td>Show synced revisions in workspace<\/td>p4 have<\/td>Helps verify client state.<\/td><\/tr>
p4 integrate (p4 integ)<\/td>Open files for branch\/merge<\/td>p4 integ \/\/depot\/dev\/… \/\/depot\/rel2\/…<\/td>Creates targets if they do not exist.<\/td><\/tr>
p4 resolve<\/td>Resolve file conflicts<\/td>p4 resolve<\/td>Run after integrate\/merge steps.<\/td><\/tr>
p4 login<\/td>Get authentication ticket<\/td>p4 login<\/td>Needed before protected operations.<\/td><\/tr>
p4 info<\/td>Display client\/server connection details<\/td>p4 info<\/td>Good first diagnostic command.<\/td><\/tr>
p4 user<\/td>Create\/edit\/delete user specs<\/td>p4 user -d sammy<\/td>Deletion and edits may require elevated rights.<\/td><\/tr>
p4 admin<\/td>Administrative server operations<\/td>p4 admin stop<\/td>Restricted to admin\/superuser roles.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Command patterns you will use most<\/h2>\n\n\n\n
Add new files<\/h3>\n\n\n\n
Use p4 add<\/strong> to open files for addition. You can set file type, assign a changelist, or force-add a literal filename pattern.<\/p>\n\n\n
p4 add -t binary file.pdf\np4 add -c 13<\/span> *\np4 add README ~\/src\/<\/span>*.c\np4 add -f *.c<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Edit, delete, and revert files<\/h3>\n\n\n
p4 edit -t text+k doc\/*.txt\np4 delete \/\/depot\/README\np4 delete -c 40 file\np4 revert \/\/depot\/...<\/code><\/span><\/pre>\n\n\n
Manage changelists and submit<\/h3>\n\n\n
p4 change\np4 change -f 25\np4 changelists\np4 submit\np4 submit -c 41<\/code><\/span><\/pre>\n\n\n
Sync and inspect revision state<\/h3>\n\n\n
p4 sync\np4 sync file.c#4<\/span>\np4 sync \/\/depot\/proj1\/...@21<\/span>\np4 have<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Integrate and resolve branch changes<\/h3>\n\n\n
p4 integ \/\/depot\/dev\/... \/\/depot\/rel2\/...<\/span>\np4 resolve\np4 submit<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Compare similar commands before you run them<\/h2>\n\n\n\n
Command<\/th>When to use it<\/th>Immediate workspace effect<\/th>Depot effect<\/th><\/tr><\/thead>
p4 add<\/td>New file should be versioned<\/td>File marked open for add<\/td>Created in depot on submit<\/td><\/tr>
p4 edit<\/td>Existing tracked file is being modified<\/td>File marked open for edit<\/td>New revision stored on submit<\/td><\/tr>
p4 delete<\/td>Tracked file should be removed<\/td>File removed from workspace and opened for delete<\/td>Deleted in depot history on submit<\/td><\/tr>
p4 revert<\/td>Discard pending local change<\/td>Open state removed; local edits discarded<\/td>No new depot revision<\/td><\/tr>
p4 submit<\/td>Finalize pending changelist<\/td>Pending open files are closed<\/td>Depot is updated with new revision metadata<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
User, authentication, and administration commands<\/h2>\n\n\n\n
These commands are commonly used during setup, troubleshooting, or admin workflows. Run administrative operations carefully, especially in shared environments.<\/p>\n\n\n
p4 info\np4 login\np4 passwd\np4 user\np4 user joe\np4 user -d sammy\np4 admin stop<\/code><\/span><\/pre>\n\n\n
P4CONFIG for repeatable local setup<\/h2>\n\n\n\n
The original post mentions P4CONFIG<\/strong>. In practice, teams often use it to keep consistent local client settings. Keep secrets out of shared files and follow your organization policies.<\/p>\n\n\n
export<\/span> P4CONFIG=.p4config\np4 info<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n
P4PORT=perforce.example.com:1666\nP4USER=your-user\nP4CLIENT=your-workspace<\/code><\/span><\/pre>\n\n\n
Common pitfalls and best practices<\/h2>\n\n\n\n
  • Open files with p4 add<\/code>, p4 edit<\/code>, or p4 delete<\/code> before<\/strong> editing workflow-critical files.<\/li>
  • Prefer numbered changelists for multi-file work; avoid large, mixed default changelists.<\/li>
  • Sync before integrate and before submit to reduce avoidable conflict resolution.<\/li>
  • Use p4 have<\/code> and p4 changelists<\/code> to verify state before submit.<\/li>
  • Be careful with wildcard patterns like *.c<\/code>; shell expansion behavior can differ by environment.<\/li>
  • Treat p4 admin stop<\/code> as a controlled maintenance action, not a routine command.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
    A practical p4 command reference for engineers who work in Perforce environments. Learn core commands, how they fit into the change lifecycle, and safer patterns for submit and merge operations.<\/p>\n","protected":false},"author":1,"featured_media":4382,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[4152,1961,4150,4154,4151,4155,4148,4149,4157,4153,3204,4147,4156],"class_list":["post-255","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-perforce","tag-list-of-p4-commands","tag-p4-command-line","tag-p4-command-line-guide","tag-p4-command-line-introduction","tag-p4-command-line-list","tag-p4-command-line-quick-guide","tag-p4-command-line-reference","tag-p4-command-reference","tag-p4-commands-for-users","tag-p4-commands-overview","tag-perforce-command-line","tag-perforce-p4-commands","tag-user-p4-commands"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/255","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=255"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/255\/revisions"}],"predecessor-version":[{"id":79083,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/255\/revisions\/79083"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4382"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}