GitHub token

Every build gets its own GitHub repository. LoopCodeLab creates that repository for you and pushes the finished code into it, so you connect a GitHub token that is allowed to do both. If the token cannot create a repository, the build ends with a push failure.

Some deliveries also run on GitHub Actions (Windows installers, Microsoft Store packages, and Google Play submissions). Those need a couple of extra permissions on the same token. If you only build web apps and media, the basic permissions are enough.

Which token type to use

You can use either kind of GitHub personal access token. Classic tokens are quicker to set up; fine-grained tokens let you scope access more tightly. Both work.

Classic personal access token

Select these scopes:

Scope	When you need it
repo	Always. This one scope both creates the repository and pushes your code.
workflow and actions:write	Windows installer or Store delivery, and Google Play submission (these run on GitHub Actions).
Secrets (repository secrets) write	Google Play submission, so LoopCodeLab can auto-wire the signing secrets your workflow needs.

Fine-grained personal access token

Set Repository access to All repositories, then set these repository permissions:

Permission	Level	When you need it
Contents	Read and write	Always. Pushes your code.
Administration	Read and write	Always. Required because LoopCodeLab creates the repository for you.
Actions	Read and write	Windows installer or Store delivery, and Google Play submission.
Secrets	Read and write	Google Play submission, for auto-wiring the signing secrets.

What each feature needs

Feature	Classic scopes	Fine-grained permissions
Build and push (all builds)	repo	Contents: Read and write, Administration: Read and write
Windows installer or Store	Add workflow, actions:write	Add Actions: Read and write
Google Play submission secrets	Add Secrets (repository secrets) write	Add Secrets: Read and write

Create the token

1. On GitHub, open your profile menu and go to Settings.
2. Scroll to Developer settings at the bottom of the left sidebar.
3. Open Personal access tokens.

For a classic token, choose Tokens (classic), then Generate new token, then Generate new token (classic). Give it a name, set an expiry, tick the scopes above, and generate it.

For a fine-grained token, choose Fine-grained tokens, then Generate new token. Give it a name and expiry, set Repository access to All repositories, add the permissions above, and generate it.

Copy the token straight away. GitHub only shows it once.

Add it in LoopCodeLab

1. Open Settings and find the GitHub card.
2. Paste the token and save.
3. Press Test. LoopCodeLab checks the token and reports the scopes it carries, so you can confirm it has what your builds need.

If a build once failed to push because the token was wrong, fix the token, save it, then press Doctor on that build. Doctor re-creates the repository and re-pushes your code, so you do not have to start over.

Pricing

A GitHub account and personal access tokens are free. GitHub Actions includes free monthly minutes that cover the delivery runs LoopCodeLab dispatches; if you run a lot of heavy builds, check GitHub’s Actions pricing (github.com pricing, as of July 2026) for what happens past the free tier.