Source control overview - BuildPixel

BuildPixel supports two source control backends:

GitHub

GitHub App installation, branch + repo picker, push triggers built in.

Perforce

Helix Core, classic depots and streams, ticket-based auth.

One organization can have one GitHub installation and one Perforce server config. A given project is single-source — pick GitHub or Perforce when you create it.

Choosing between them

	GitHub	Perforce
Best for	Code-heavy projects, indie / mid-size teams	Asset-heavy projects, classic UE workflows
Auth	GitHub App install	Username + password, or P4 ticket
What you connect	A repository	A depot path or a stream
Push triggers	Built in	Via custom Helix trigger script

If your team is already committed to one or the other, use that. If you’re choosing fresh, GitHub is the lighter setup; Perforce is the better fit for projects with very large binary content trees.