Connect GitHub¶
Forge reads your source through a GitHub App called Mithran MAP Sandbox. The control plane uses it to clone your repo at build time, so there are no deploy keys or personal access tokens involved. You install it once on the account (personal or org) that owns the repos you want to deploy.
Install it through the setup link¶
The right way to install is to start from Forge, not from GitHub:
When setup needs the App, it gives you a link. Open that link. It carries a one-time token that ties the install back to your Mithran account, so the moment GitHub finishes the install, Forge knows the App belongs to you.
Why not just go to the App's GitHub page?¶
You can install the App directly from github.com/apps/mithran-map-sandbox, and GitHub will happily install it. But that path skips the token above. GitHub then bounces you to a page that reads:
That looks alarming. It isn't fatal: the App is still installed on GitHub. What failed is the bookkeeping that links the install to your account. If you see this, the fix is to run aegis setup and use the link it gives you so the connection gets recorded.
Repository access¶
When GitHub asks which repos the App can touch, either grant All repositories or pick the specific ones you'll deploy. You can change this later in your GitHub settings under Settings → Applications → Mithran MAP Sandbox → Configure.
A brand-new private repo can lag
If you create a private repo and install the App moments later, GitHub sometimes takes a while to let the App's token reach that repo over git. The REST API will say the repo is visible while git clone still 404s. It's a GitHub-side cache, and it clears on its own. If your first deploy fails fetching source on a just-created private repo, wait a few minutes and re-run it. See Troubleshooting.
Check the grant¶
Look for the GitHub App and repo-grant fields. Green there means onboarding will work.
Next¶
Configure your app with a mithran.yaml, or jump to Onboard a repo.