Perforce

version control

Backlinks¶

• avoid developing Unity projects on Dropbox
  • The unity library is by default also uploaded, which unnecessary increases the project size and creates conflicts. This should be excluded from your version control, e.g. with a git ignore on git, or a perforce ignore on Perforce
• python-perforce
  • a pure Python Perforce API
• P4V
  • UI client for Perforce
• Perforce Python workspace-client
  • find the active Perforce workspace (=client) in Python with python-perforce
• Perforce setup workspace
  • Perforce
• Subversion
  • also see git, and Perforce
• Unreal game sync
  • Unreal game sync pulls a Perforce repo, which contains both the Unreal project & editor.
• change caps for a committed file
  • Perforce won’t let you do this by default it it runs on a Windows server. (see article)
• common source control mistakes
  • versioning inside source control. e.g. uploading a v1, v2, v3 to a git or Perforce repo
• local Unity tools - Git
  • This setup assumes you use git, and creates a local folder that is ignored by git to store your tools in. Other version control software (e.g. Perforce) should also support ignore files.
• pyforce
  • a full typed Perforce API in Python