Pull requests and CI
Accounts
Section titled “Accounts”Pipelines → Connect GitHub or Connect GitLab signs in with the browser: ffgit shows a code, opens the provider’s page and waits for your approval. A personal access token works too. GitLab connections ask for the api scope by default, so job actions, reviews and merges work; GitLab sign-ins renew themselves.
Provider account profiles are kept per workspace; their tokens are stored locally in an encrypted file. Workspaces and projects choose which profile they use, and a profile can carry an SSH key, or a saved token for Git over HTTPS.
Clone repository… can list a verified GitHub or GitLab account’s repositories, 30 a page and searchable by name, and fills the URL and folder from the one you pick.
Pull and merge requests
Section titled “Pull and merge requests”- Lists of pull requests (GitHub) and merge requests (GitLab) for the project.
- Diffs and images, with the same image viewer as local changes.
- Inline draft comments, discussions and replies; approve or request changes.
- Viewed on a file folds it and the header counts viewed files. A file that a later push changed reads Changed since viewed. On GitHub this is GitHub’s own mark, so it carries to github.com and back; on GitLab ffgit keeps it with the review’s drafts.
- Merge offers only the methods the project allows, suggests squash when the commits read like wip or fix, and asks for confirmation.
Drafts are restored with the window, and guards against stale diffs and uncertain writes prevent a review from being sent twice.
Create a pull or merge request
Section titled “Create a pull or merge request”Create pull / merge request… in repository actions, or on a chat’s request card, opens a GitHub pull request or GitLab merge request from the checked-out branch: the source and target repository (a fork’s upstream by default), the base, what it brings, an editable title and description and Open as a draft. Your agent can draft the title and description from the branch’s changes. Where it goes is confirmed before anything is sent.
Pushing stays in Git actions: the provider’s branch must be the commit you reviewed. An open request from the branch is opened instead of a new one, and the request is linked to the worktree and its chat.
Start a chat from an issue
Section titled “Start a chat from an issue”Start chat from issue… in repository actions reads a GitHub or GitLab issue by number or link, shows what your account may do there, and puts the issue into New chat’s message box as a task. Nothing starts until you send it, and nothing is written to the provider.
Review guide
Section titled “Review guide”Review guide… on an open request has your agent — Claude Code or Codex, the one chosen in Coding agents settings — read it in a temporary checkout and write a tour in reading order: Look closely where only a maintainer can decide, mechanical changes last, and every file somewhere. The checkout is a detached worktree in the system’s temporary folder, removed once the guide is written. Each file in the guide opens in the review, Comment… at a stop adds to the review’s summary draft, and the guide is kept with the review’s drafts.
Pipelines
Section titled “Pipelines”Pipelines shows CI runs with filters for workflow, event, actor, source and name. When the host names the provider, ffgit picks it for you.
- A run’s header has a strip of its stages, each marked with what its jobs’ latest attempts sum to; a click opens that stage in Jobs.
- Jobs group by stage in the pipeline’s order. All | Failed N lists only the jobs whose latest attempt failed. A pipeline that passed with allowed failures reads Warning.
- A job’s log keeps the job’s colors, folds into GitLab sections and GitHub groups, and has search.
- Run, retry or stop a job, and retry a failed run’s failed jobs. A running pipeline stops from its header, and ▶ runs a new GitLab pipeline on a ref with its variables, or a GitHub workflow that declares
workflow_dispatchwith its inputs. Each write first shows the project, ref, every value and the access it needs. - Running pipelines refresh in place while their window is visible.
- A pull or merge request shows the checks the merge requires apart from the head’s CI: GitHub’s rulesets and branch protection, GitLab’s Pipelines must succeed and status checks.
Artifacts and golden failures
Section titled “Artifacts and golden failures”- Download artifact ZIPs with progress in bytes; downloads are verified.
- Preview files and images inside an artifact, save it, or compare it with an artifact ZIP you saved earlier.
- Golden-test failures are grouped with Expected/Actual, isolated-diff and masked-diff views — see Image review.