Skip to content

Connecting a Git provider

AppArch registers projects through a Git credential. Add one under Credentials → Add credential: pick the provider, follow the provider-specific setup the wizard shows, then paste the values.

ProviderHow it authenticatesSupported hosting
GitHubPersonal access token (fine-grained or classic)github.com only
GitLabOAuth application or personal access tokengitlab.com or a self-managed GitLab
BitbucketOAuth client or workspace / repository access tokenBitbucket Cloud only
Azure DevOpsPersonal access tokenAzure DevOps Services (dev.azure.com) only

A pasted token is checked with the provider before it is stored; an invalid or expired token, or one without read access, is refused. Credentials are stored encrypted.

Create a token under Settings → Developer settings → Personal access tokens: a classic token with the repo scope, or a fine-grained token with read access to your repositories (plus Pull requests: Read and write for ArchPilot comments). Details: GitHub.

Choose gitlab.com (Cloud) or Self-hosted (enter your instance URL), then either:

  • Register an application - an OAuth application with the scopes api, read_user, read_repository; finish with Connect with GitLab.
  • Paste a token - a personal access token with api, or read_api for read-only use.

Details: GitLab.

Bitbucket Cloud only. Either:

  • Register an application - an OAuth client created under Workspace settings → OAuth clients; finish with Connect with Bitbucket.
  • Access token - a workspace or repository access token with repository and pullrequest.

App passwords are not offered. Details: Bitbucket.

Create a PAT with Code (Read & Write) and Pull Request Threads (Read & Write), then enter only the organisation slug (the part after dev.azure.com/) and the PAT. Details: Azure DevOps.

There is no generic or SSH-based Git connection. The only self-hosted server AppArch can reach is a self-managed GitLab - see Self-hosted Git.

Once the credential is ready, register a project.