This is a quick cheat sheet guide for git users trying to migrate over to perforce. It does not include an exhaustive list of commands, this is just a simple cheat sheet to get people started.<\/p>\n\n\n\n
<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" This is a quick cheat sheet guide for git users trying to migrate over to perforce. It does not include an exhaustive list of commands, this is just a simple cheat sheet to get people started. Command Git Equivalent Perforce Documentation Notes p4 sync git pull \/ git fetch https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_sync.html p4 integrate git merge https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_integrate.html … <\/p>\nCommand<\/td> Git Equivalent <\/td> Perforce Documentation<\/td> Notes<\/td><\/tr> p4 sync<\/td> git pull \/ git fetch<\/td> https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_sync.html<\/td> <\/td><\/tr> p4 integrate<\/td> git merge<\/td> https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_integrate.html<\/td> <\/td><\/tr> p4 opened<\/td> git status<\/td> https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_opened.html<\/td> The git status command isn’t a direct equivalent of p4 opened. However, p4 opened will show what files you have checked out that are not yet submitted. <\/td><\/tr> p4 edit<\/td> git checkout<\/td> https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_edit.html#p4_edit<\/td> The git checkout command is usually used for checking out a branch, there is no direct equivalent in git for p4 edit. All files in p4 must be “checked out” first before they can be checked in. <\/td><\/tr> p4 submit<\/td> git push\/git commit<\/td> https:\/\/www.perforce.com\/manuals\/cmdref\/Content\/CmdRef\/p4_submit.html#p4_submit<\/td> In git you usually have to do a git commit command and then a push. In p4, it’s all in one command, and you submit a “changelist”<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n