Skip to main content
Help Center

Connect a Source Repository to Batoi Build

Link the app to its canonical GitHub repository and verify branch, synchronization, and delivery ownership.

3 min readVerified Jul 24, 2026Batoi Platform
Guide navigation 5 of 42
Browse all 42 articles
Business view

What this page helps you accomplish

Link the app to its canonical GitHub repository and verify branch, synchronization, and delivery ownership.

Batoi Platform · Build
Accountable roleWorkspace Admin, Builder
Business taskIntegration
Completion signalThe app points to the approved GitHub repository and branch, reports an honest synchronization state, and has clear delivery ownership.
1 Confirm

Scope and authority

An active Batoi Build app in the intended workspace Access to the approved GitHub organization and repository

2 Act

Integration

Link the app to its canonical GitHub repository and verify branch, synchronization, and delivery ownership.

3 Verify

Observable business result

The app points to the approved GitHub repository and branch, reports an honest synchronization state, and has clear delivery ownership.

Potential issue and recovery

The expected record or action is missing.

Recommended recovery: Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.

Who should use this article

This article is for Workspace Admins and Builders who are authorized to complete or review this task. A consequential decision remains with the accountable person.

Before you begin

  • An active Batoi Build app in the intended workspace
  • Access to the approved GitHub organization and repository
  • Authority to assign repository synchronization and delivery ownership
  • Use approved sample or operational information only. Never enter a password, token, private key, or unnecessary personal information.

Open repository settings

  1. Open the selected app in Build.
  2. Expand Settings and choose Repositories.
  3. Use App Workspace after linking to review source-of-truth and synchronization status.
Repository connection and ownership workflow The approved GitHub repository is linked to the selected app, synchronization is configured, and an owned delivery pipeline consumes the reviewed branch. Repository readiness has four parts Canonical GitHub Approved organization and repository App Link Provider, URL, and default branch Synchronization Reviewed branch and explicit refresh owner Pipeline Owner CI/CD responsibility and evidence
A repository can be linked while synchronization or pipeline ownership remains incomplete.

Connect the repository

  1. Confirm the approved GitHub organization and repository already exist or create them through the authorized organization workflow.
  2. Select GitHub as the provider and enter or choose the canonical repository.
  3. Set the default branch to the repository standard, such as main.
  4. Save the app-scoped repository record.
  5. Open the repository at GitHub to verify visibility and organization policy; the Build register may not display visibility.
Batoi Build repository register
Reference screen: confirm the selected app filter, canonical repository, and branch.

Verify the operational connection

  • The repository belongs to the intended organization and app.
  • The default branch matches GitHub.
  • App Workspace identifies GitHub as the source of truth.
  • Repository synchronization has an honest configured or setup-needed state.
  • A CI/CD pipeline owner is assigned before automated delivery is relied upon.
  • The connected repository remains the source of truth for the application.
Batoi Build repository register
Reference screen: use App Workspace to identify a linked repository whose synchronization still needs configuration.

Continue with Prepare a Sandbox Environment in Batoi Build.

Troubleshooting and recovery

What you seeWhat to checkSafe next action
The expected record or action is missing.Workspace, project/app context, role, status filters, and prerequisites.Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.
The status remains incomplete or needs review.Required fields, evidence, approvals, source connections, checks, and owners.Record the missing item and owner. Do not mark the task complete until it can be independently verified.
The result conflicts with policy or evidence.Scope, source recency, exception authority, decision conditions, and reviewer independence.Do not bypass the control. Return the item for correction or escalate it through the authorized route.

Safety and governance

Protect sensitive information. Do not place credentials, secrets, private keys, raw tokens, unnecessary personal information, private repository content, customer identifiers, or restricted documents in a public note, screenshot, prompt, export, or evidence caption. Use approved secret references and permission-controlled workspace records.

Final verification

Expected result: The app points to the approved GitHub repository and branch, reports an honest synchronization state, and has clear delivery ownership.

Next step

Continue with the next verified article in this Product Guide, or return to the Batoi Platform Product Guide.