Manage Git

Connect GitHub, GitLab or Bitbucket once. Alloy creates the repository, opens a pull request for every new version, lets you edit and merge it, and imports changes you make outside Alloy.

Connect a provider

1. Open a project in the Studio and click Manage Git (Pro).
2. Choose GitHub, GitLab or Bitbucket and click Connect.
3. Approve Alloy on the provider's page. You come back to the Studio already connected.

Your access token is stored encrypted and is only used for this project's repository. You can disconnect at any time.

First push

Pick a repository name and whether it is private (the default), then click Create repository and push. Alloy creates the repo and commits the whole project to its default branch (usually main).

Branches and pull requests

• After the first push, every new version goes to its own branch, such as alloy/add-pricing-v2.
• Alloy opens a pull request (merge request on GitLab) into main, with the prompt, the changed files and a preview link in the description.
• While that pull request is open, more versions add commits to it: the button reads Push commits to PR #n.
• Your main branch is never written by Alloy after the first push.
• Every prompt on a linked project pushes automatically, so the repo always matches the Studio.

Edit and merge

In the Manage Git dialog you can change the pull request title and description and click Save changes, then Merge into main. Merging on the provider's website works too; Alloy notices the next time you open the dialog.

Import changes made outside Alloy

Edited the code in Cursor, Claude Code or by hand and pushed to main? Click Import changes from main. Alloy compares three versions: what is on main, what is in Alloy, and the last version both agreed on.

An import is saved as a new version labeled [external], so your next prompt builds on the imported code.

Change repo

Once linked, the Studio button shows the provider icon, owner/repo and the number of open pull requests. In the dialog, Change repo unlinks the project. The repository itself stays on the provider; the next push creates a new one.

Provider notes