T3 Code integrates with GitHub, GitLab, Bitbucket, and Azure DevOps to clone and publish repositories, create pull requests, and review changes.
Install Git and configure authentication on the machine running your T3 Code server. For a remote environment, do this on the remote machine. After signing in, open Settings → Source Control and choose Rescan.
Install GitHub CLI 2.81.0 or newer, then sign in:
gh auth loginInstall GitLab CLI, then sign in:
glab auth loginSet an access token in the server's environment:
export T3CODE_BITBUCKET_ACCESS_TOKEN="your-access-token"Or use an Atlassian account email and API token with read/write access to repositories and pull
requests, plus user read access (read:user:bitbucket):
export T3CODE_BITBUCKET_EMAIL="you@example.com"
export T3CODE_BITBUCKET_API_TOKEN="your-token"The access token takes precedence if both are configured. Restart the server after changing these variables.
Install Azure CLI, add the DevOps extension, and sign in:
az extension add --name azure-devops
az loginUse Add Project in the command palette (Cmd/Ctrl+K) to clone a repository. Choose a hosting
provider or paste a Git URL, then choose where to save it.
For a local Git repository without a remote, Publish Repository creates a hosted repository,
adds it as origin, and pushes your commits. If there are no commits yet, it creates the remote;
make your first commit before pushing.
Use a thread's Git actions to commit, push, and create a pull request. T3 Code can generate commit messages, review titles, and descriptions from your changes.
Choose the writing style and model in Settings → Source Control. Repository conventions uses the project's instructions and recent commit subjects.
Open Pull requests to review changes and comments, request reviewers, check out a branch, or merge. You can edit review titles and descriptions and your own comments where the host allows it. GitLab calls these merge requests.
GitHub, GitLab, and Azure DevOps support auto-merge while checks are outstanding. GitHub also supports approving waiting fork workflows and opening a revert pull request for a merged change.
For Azure DevOps, use the host website to view diffs or change comments. Bitbucket does not support reopening a declined pull request.
- Not authenticated: run the provider's login command on the server, then rescan. For Bitbucket, confirm the running server received the environment variables.
- GitHub sign-in cannot be verified: update GitHub CLI to at least 2.81.0.
- Push fails despite a connected account: check the Git remote's credentials. SSH and HTTPS remotes can require separate setup from the hosting provider's API access.
- A review cannot load: open it on the host website while resolving connectivity, permissions, or rate limits.