Pull requests and GitHub

Fleet can follow the GitHub issues and pull requests that belong to a session. You see their state, checks and reviews next to the conversation, and you can hand a failing check or a review comment to the agent with one click.

Choose Connect GitHub in a session’s Context tab. It shows when a link needs a sign-in, and opens the GitHub integration page.

• Connect with GitHub uses the device flow. Fleet shows a Device code. Choose Open GitHub, enter the code there, and Fleet finishes the connection by itself. This is the recommended way.
• If the device flow isn’t available, paste a personal access token instead. Fleet checks the token before it stores it.

Once connected, the page says GitHub is connected. Disconnect forgets the token. Sessions keep their links, but the links stop updating.

There are two ways.

From the new-session page. Pick a folder whose repository is on GitHub, then type # in the message box. A list of open pull requests and issues in that repository appears. Keep typing to filter it.

• Press Enter to start a session from the one you picked.
• Press Shift+Enter to open the session that already works on it. Items that have one are marked has a session.

The item shows as an attachment on the message. Add your own instructions, then send. For a pull request, the new branch is named after the pull request’s branch.

From GitHub in Fleet. Choose the GitHub icon on the left rail and open an issue or pull request. The main button reads Start a session, or Start a session on this branch for an open pull request. If a session already exists it reads Open session instead. The In Fleet list shows the sessions that work on the item.

Open Context in the panel on the right. It lists what is linked to the session.

• Started from shows the issue or pull request the session began with, or the automation that started it.
• This session’s pull request shows the pull request the session opened or works on. Fleet finds it from the conversation, from the output of gh pr create, and from the session’s branch.
• Pinned and Mentioned in conversation hold other links. Pin one to keep it, or dismiss it.
• Workspace shows the session’s branch and folder.

To add one yourself, choose Attach a pull request or issue and paste its address.

A pull request card shows its state, such as Draft, Checks running, Changes requested, Ready to merge or Merged. It also shows the branch it merges into and the lines added and removed. A merged pull request is no longer checked.

• Checks lists each check. Open it and choose Send to agent on a failing one. Fleet sends the failure to the session as a message.
• Reviews shows who approved, asked for changes or is still to review.
• Review lists unresolved review threads with the file and line. Choose Send to agent on a thread to pass the comment on. The button then reads Sent.
• Merge conflicts appears when the branch conflicts with its base.

On an item’s page under GitHub, one button sends everything at once. It reads Fix failing checks, Address review, or Fix checks and address review, depending on what is open.

• Reviewing a session: read the diff before you open the pull request.
• Automations: start sessions without typing the first message.
• Sessions and worktrees: where the branch and worktree come from.