Forges and pull requests

MyTwig works with GitHub, GitHub Enterprise Server, GitLab (gitlab.com and self-managed), Gitea and Forgejo (including Codeberg), and Bitbucket Cloud.

Sign in

Settings → Accounts lists every account MyTwig can use and where its token is kept.

GitHub and GitHub Enterprise: Add GitHub Account… signs in to github.com or your server (type its host or URL). Two ways:

• Personal access token. Create a Token… opens the right page with the scopes MyTwig needs (repo, read:org, notifications, workflow). MyTwig checks the token and shows who it belongs to.
• GitHub CLI. If you’ve run gh auth login, MyTwig uses gh’s accounts on every host automatically.

MyTwig also finds $GITHUB_TOKEN, $GH_TOKEN, and tokens your Git credential helper keeps for github.com.

GitLab, Gitea, Forgejo, Bitbucket: Other accounts signs in with a token (for Bitbucket, your email and an Atlassian API token, or a username and app password). $GITLAB_TOKEN is used too.

Tokens you sign in with are kept in the system keychain (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux). They’re never written to disk or logs.

When you have several accounts, a repository uses its owner’s account, then one that belongs to the owner’s organization, then your default. The profile menu can pick another per repository.

Pull requests and issues in the left panel

The left panel lists the open pull requests (merge requests on GitLab) and issues of the repository. Choose one to see it in the details panel: who opened it, its branches and labels, its description, and buttons to check it out, create a branch, or open it in the browser. Its head commit is chosen in the graph.

Branches with an open pull request show its icon beside their label, colored by state, with review and CI status on hover.

Create a pull request

• Drag your branch onto a remote branch in the graph or left panel. MyTwig pushes it and opens the Create Pull Request dialog with that branch as the base.
• Or use Create Pull Request from a branch’s menu, the working tree panel’s next steps, or the palette.

The dialog starts from your repository’s pull request template. With an AI provider set, it can write the title and description from your commits and diff.

Check out a pull request

Check Out in a pull request’s details fetches it and checks out a branch for it, including pull requests from forks. From the menu bar, a pull request can be checked out into a worktree of its own.

Review a pull request in the app

Review Pull Request (GitHub for now), from a pull request’s menu, its branch’s menu or the palette, opens it in the middle of the window:

• every changed file, compared with where it left its base;
• review threads under their lines, to reply to, resolve or unresolve;
• click any line’s gutter to start a comment;
• finish with Approve, Request Changes or Comment, or merge, squash or rebase it when it’s ready.

Issue links

Settings → Git can turn text in commit messages into links, for example JIRA-\d+ to your tracker. ${0} is the match and ${1}… its groups. GitHub’s own #123 links work without setup.