Alloyqa
DocsSecurityModelsiOS & macOSPrivacyPricingDownloads
Log inSign up
Contents01How GitHub works02Connect GitHub03Repository access04Public repository Tasks05Permissions06Disconnect & troubleshooting
GitHub integration

Your code,
connected carefully.

Alloyqa for GitHubRepository-scoped access6 sections

Connect selected GitHub repositories through the Alloyqa GitHub App, or run a Task against a public GitHub repository without connecting GitHub. Connected repositories can use short-lived credentials to create branches, push changes, and open pull requests. Public repository Tasks are cloned anonymously and remain in Alloyqa for review. They cannot push or merge.

01

How GitHub works

Alloyqa for GitHub

Choose a connected repository or a public GitHub repository URL for a Task.

Connected repositories use the GitHub App installation flow. Public repository Tasks use a separate public-source path and do not require a GitHub connection.

02

Connect GitHub

  1. 1
    Choose Connect GitHub

    Start from Settings → Integrations, or from the repository prompt in New Task.

  2. 2
    Authorize the GitHub App

    GitHub opens its installation screen, where you choose the account and repositories the App can access.

  3. 3
    Return to Alloyqa

    The signed callback records the installation and refreshes the repository list for the current workspace.

03

Repository access

For connected-repository Tasks, Alloyqa only exposes repositories returned by your GitHub App installation. When you select one, Alloyqa checks that the connection belongs to the current workspace.

The worker receives an explicit repository allow-list. The server requests the smallest runtime profile needed, then mints short-lived installation credentials for the selected repository and verifies the returned permissions and repository association.

Connected Task code is checked out temporarily in an isolated, job-scoped Cloud workspace. The checkout and execution infrastructure are cleaned up after the work is finished.

Stored integration credentials are encrypted at the application layer.

Repository selection is scoped.Connecting GitHub does not make every GitHub repository available to Alloyqa. GitHub's installation selection and the repository you choose in the Task composer both apply.
04

Public repository Tasks

You can provide a public HTTPS GitHub repository URL without connecting GitHub. Alloyqa verifies the URL, retrieves the source anonymously over HTTPS, and runs the Task in an isolated Cloud workspace.

Public-repository Tasks do not receive GitHub App or write credentials. Resulting changes are retained in Alloyqa for review and are not pushed to GitHub, used to create pull requests, or available for merge.

05

Permissions

For connected repositories, the runtime requests permissions by operation. The strongest agent profile is used for Alloyqa execution; read-only profiles are used for repository picking, review, previews, and merge checks.

PermissionAccessWhy it is used
MetadataReadRequired by GitHub for repository identity.
ContentsRead / writeRead code; create commits and branches for Task execution.
Pull requestsRead / writeRead PR context and create or update pull requests.
WorkflowsWriteNeeded only when a Task modifies files under .github/workflows/**.
Commit statusesReadRead verification status for review and repair decisions.
IssuesReadRead pull-request conversation comments.
ChecksReadRead check-run results alongside commit statuses.

The exact permissions shown by GitHub are controlled by the installed App and may reflect the combined permissions requested by the current Alloyqa operation.

06

Disconnect & troubleshooting

Use Settings → Integrations to reconnect GitHub or update the repositories available to Alloyqa. Reconnecting refreshes the installation reference and reconciles the current repository list.

Disconnecting removes Alloyqa's stored GitHub installation reference and GitHub workflow configuration for the workspace. To revoke the App's access at the GitHub level as well, remove the Alloyqa App installation in GitHub.

Disconnecting does not erase historical Task, pull-request, or review metadata already stored in Alloyqa.

Alloyqa does not autonomously deploy production changes; review and merge remain part of the connected-repository Task path you choose.

No repositories appear

Open Settings → Integrations and reconnect or update the GitHub App installation, then refresh the repository picker. If no connected repositories are available, you can use a public GitHub repository URL instead.

Connect GitHub opens again after canceling

Canceling or closing the GitHub page before the callback completes does not connect anything. Return to Alloyqa and start a new attempt; the Task draft remains local to the composer where supported.

A Task says the repository is unavailable

Confirm that the repository is still selected in the GitHub App installation and connected to the current workspace. Reconnect GitHub if its permissions or installation changed.

A pull request or check cannot be read

Reconnect GitHub if the installation permissions need updating. Alloyqa checks the permission response and reports when an operation needs the installation to be updated.

Contact Alloyqa about a security or access concern →

Alloyqa
Security at Alloyqa →
DocsSecurityModelsvs Codex Cloudvs Cursor CloudPrivacyTermsContact
© 2026 Alloyqa