Pull & merge requests

Wyrm talks to GitHub and GitLab directly, so you can see and manage the pull requests (merge requests on GitLab) for the work in front of you without leaving the log. In the app both are called Pull Requests.

Connect an account

Open Settings… (⌘,) → Integrations. There is a group for GitHub and one for GitLab.

• GitHub: click Connect GitHub. Wyrm shows a short code (Enter this code on GitHub:). Click Copy code, then Open GitHub, paste the code and approve. The app finishes on its own once GitHub confirms.
• GitLab.com: click Connect GitLab and approve Wyrm in the browser.
• Self-hosted GitLab or a personal token: choose Use a token instead / add a self-hosted instance. Enter the Host (host name only, e.g. gitlab.example.com) and a Token, then Verify and connect. Wyrm checks the token first and saves it only if it works. The required scopes are listed under Required token scopes: repo, read:user for GitHub, api for GitLab.

A connected account shows Connected as …. Tokens go into the macOS keychain. To remove one, open the row’s menu and choose Disconnect…; Wyrm deletes the token from the keychain.

The Pull Requests panel

Once the repository’s remote matches a connected account, a Pull Requests button appears in the icon rail on the left. The panel lists the open pull requests for the nearest bookmark and refreshes every minute (or click Refresh).

Each row shows the number and title, a CI result (✓, ✗ or ⏳; hover for the check count), the state (Draft, Open, Merged, Closed), a Conflicts pill when the branch no longer merges cleanly, and the reviewers with their review state. CI results also appear as badges on commits in the log. Right-click a row and choose Open in browser to jump to the forge.

If the panel says No forge connection for …, click Open Integrations settings and connect the account for that host.

Open a pull request

1. Give the commits you want to propose a bookmark (B with a commit selected).
2. In the Pull Requests panel, click Create Pull Request at the bottom.
3. Fill in the form:
   • Title and Description (the description is filled from the commit).
   • Source bookmark: defaults to the nearest bookmark. Bookmarks that exist only on your machine are tagged Local only — pushed on create.
   • Target bookmark: defaults to your trunk (main, master or develop).
   • Reviewers and Draft, if you want them.
4. Click Create Pull Request. If the source bookmark isn’t on the remote yet, the button reads Push & Create PR and pushes it first. If your local bookmark is ahead of the remote, Wyrm warns you and offers Create without pushing or to push those commits first.

Wyrm shows Pull Request Created! with a link. A half-filled form survives closing the panel.

Edit, review and merge

Click a row to open the pull request in the revision pane. From there you can:

• Edit title and Edit description (Markdown is rendered).
• Switch between Mark ready and Mark draft.
• Add or remove Reviewers.
• Merge an open pull request that can be merged. Pick the Merge method (Merge commit, Squash or Rebase) and confirm. A merge can’t be undone from Wyrm. If the forge is still waiting for a required pipeline or approval, Wyrm tells you to check the pull request in the browser.

Comments, approvals and review threads stay on the forge: use Open in browser for those.

What needs Pro

On public repositories everything above is free, as are repositories on self-hosted servers.

A private repository on GitHub, GitLab.com or Bitbucket needs Pro (or the 14-day trial) for any work, pull requests included. On Free, Wyrm opens it behind a “This is a private repository” notice, and the pull-request form shows “Pro required to create pull requests on private repositories.” See Account, trial & billing.