- Workflows > PR Autopilot for commits, pull requests, and PR monitoring.
- Integrations > GitHub for your GitHub connection, commit identity, and branch naming.
PR Autopilot
The pane has five groups. Changes apply as soon as you change a control.Commits
With Generate commit messages on and Skip commit confirmation off, the commit form opens with a generated message for you to review before you commit.
Pull Requests
Skip PR Confirmation works for GitHub repositories on github.com. To see the sheet for a single PR, Shift+click Open PR.
PR defaults
This group has no heading.PR Monitoring
Turning off Monitor PRs hides the two merge controls. See PR monitoring below for how it works.
PR Template
FlowDeck uses the template when it generates a PR title and description.- Title defaults to
[title]. - Description has sections for what changed, why, how, testing, and notes.
[brackets] guides the agent and is not included in the PR. When you change a template, Reset to default appears under it.
GitHub
The GitHub pane has three groups.Connection
The top row shows Not connected, or Signed in as your GitHub username. Click Connect GitHub to sign in. Click Disconnect and confirm to sign out. After you disconnect, you need to reconnect to open or manage pull requests. If FlowDeck cannot finish setting up Git access for your account, a note appears with a Retry button. If it cannot clean up after you sign out, a note appears with Try Again. Some notes also offer Forget, which stops FlowDeck tracking the credential without deleting anything from your Keychain.Commit Identity
Enter a Name and Email and click Save. FlowDeck uses them for commits it creates only when Git’s ownuser.name or user.email is not set for the repository. They do not change your Git configuration. To remove a saved identity, clear both fields and click Clear.
Automatic Branch Naming
PR monitoring
When Monitor PRs is on, FlowDeck checks each open or draft PR about once a minute. It watches the sessions that are open in FlowDeck. Closed sessions keep the last status they had until you reopen them. What happens depends on the PR:- Checks fail or the PR has a merge conflict. FlowDeck sends the agent a message that names the problem and asks it to fix it and push. FlowDeck only messages an agent that is idle and not waiting for your answer.
- The agent does not fix it. FlowDeck asks again every five minutes, up to three more times. After that, the status becomes Needs Attention and FlowDeck stops asking.
- Checks are still running, or the PR waits for a review. FlowDeck waits.
- Every check passes and the PR is mergeable. With Automatically merge monitored PRs on, FlowDeck merges it with your chosen method. With it off, the PR stays open for you to merge. If GitHub rejects the merge, for example because a review is required, FlowDeck tries again later.
- The PR is merged or closed. Monitoring for that PR ends.
What you see
In a monitored session, a banner above the message box shows PR monitored and the PR’s status, for example PR #42 - Checks Running. The status is one of:- Checks Running
- Checks Failed
- Merge Conflicts
- Pending Approval
- Ready
- Draft
- Merged
- Closed
- Needs Attention
Monitoring runs only while FlowDeck is open. Monitoring and automatic merging are settings, not permission to bypass an approval request for a remote change.

