Git integration
By default, Flight Plan uses the git command to read and fetch your local and remote branches and their commits. That’s local git. It needs no account and is always on, so you can skip this step.
Connecting a code hosting site, such as GitHub, GitLab or Bitbucket, lets Flight Plan do more:
- fetch the open pull requests of you and your team members,
- read the comments and reviews on a pull request,
- add comments and submit reviews,
- and use most of the other features your git provider offers.
| Option | How it connects |
|---|---|
| GitHub CLI | Uses gh and its own sign-in. |
| GitLab CLI | Uses glab and its own sign-in. |
| GitHub token | GitHub or GitHub Enterprise, with a token. |
| GitLab token | GitLab or self-managed GitLab, with a token. |
| Bitbucket | Bitbucket Cloud with a username and a token, or Data Center with a token. |
A command line option shows Signed in as and your account once you have signed in with the tool. Until then it’s Unavailable, with what to do.
A token option asks for:
- Token. It goes into your system keychain and is never shown again. When a token is already saved, leave the field empty to keep it.
- Base URL, only for a self-hosted site, such as
https://git.example.com. Leave it empty for the cloud.
On Settings → Git integration, Pull pull request data every … minutes sets how often Flight Plan asks your code hosting site for pull requests again. It’s 10 minutes unless you change it, and takes a whole number of minutes from 1 to 60. Local git keeps fetching on its own, at most every five minutes.
Skip for now keeps local git only. You can connect a site later under Settings → Git integration.
There is no default to choose. Each repository uses the connection that serves its remote’s host, and local git when none does. See Git connection for how Flight Plan matches them.