> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildpixel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Source control overview

> GitHub or Perforce. Pick the integration that matches your team.

BuildPixel supports two source control backends:

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/source-control/github">
    GitHub App installation, branch + repo picker, push triggers built in.
  </Card>

  <Card title="Perforce" icon="diamond" href="/source-control/perforce">
    Helix Core, classic depots and streams, ticket-based auth.
  </Card>
</CardGroup>

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.