GitHub Quick Start Guide

Connecting GitHub

1. Go to Settings in the workspace

2. Click Connect GitHub

3. Authorize Airbuild via OAuth

4. Select an existing repository, or create a new one straight from Airbuild

5. Choose the branch to bind to

One repository per project. The binding can be changed or removed at any time.

Auto-Commits

After each AI change, Airbuild automatically commits to your linked repository. Each commit describes what was changed.

Branches

Every chat creates its own Git branch. This keeps different conversations and their changes isolated.

Pull Requests

Create pull requests directly from Airbuild:

• Click the Git button in the toolbar
• Select Create Pull Request
• Choose base and target branch
• Add a title and description

Working with Your Team

When team members work on the same project:

• Each person's changes go to their own branch
• Use Pull Requests to merge changes
• Airbuild handles merge commits (never rebases)

Source Control Panel

The Source Control panel in the toolbar shows:

• Current branch
• Changed files
• Commit history
• Push/pull status

When a Merge Conflicts

Conflicting files are listed with two ways out: Resolve with AI, where the agent works through the conflict, or Resolve Manually, where you pick per conflict — ours, theirs, both, or edit it yourself. The merge button stays disabled until every conflict is settled, and says so.

Commit Messages

The commit box has Suggest message with AI — the agent reads the staged changes and proposes a message. Useful when a turn produced a dozen files and you would rather review a summary than write one.

Deploying from a Branch

A deployment target remembers which branch it builds from — pick it from your repository's branches instead of always shipping main. The branch is brought up to date before the publish starts, so a colleague's push is part of the release instead of quietly missing.

Tips

• Link your repo early — it's easier to set up before generating code
• Use descriptive chat messages — they become commit messages
• Create separate chats for separate features (each gets its own branch)
• Pull before you start, to avoid conflicts later

The full integration — commit history, per-file diffs, PR management, team workspaces — is documented under GitHub.