Pull requests

Glueprint can create a pull request from the current branch without leaving the Worktree view. Today this is GitHub-only and goes through the GitHub CLI (gh).

Prerequisites

• gh installed on the machine that hosts the working directory. Install instructions: cli.github.com.
• gh auth status clean — run gh auth login once if you haven’t.

If either is missing, the Create PR modal opens with a message explaining the issue and a link out. Everything else in the Git section works without gh.

How to open one

1. Make sure your branch has commits the remote doesn’t, and is published. (Run Publish from the commit bar if it isn’t.)
2. Open the Create PR modal — from the Git panel’s PR action.
3. Fill in:
   • Title — pre-filled from your last commit subject.
   • Description — pre-filled from the commit body, if any.
   • Base branch — the branch you want to merge into. Defaults to your repo’s default branch.
4. Click Create PR. Glueprint shells out to gh pr create and shows the resulting PR URL on success.

Where it goes

The PR is created against the upstream remote of the current branch — usually origin. Glueprint doesn’t second-guess the remote you’ve configured; whichever GitHub repo gh resolves for the branch is where the PR lands.

What it doesn’t do

• Other forges — GitLab, Bitbucket, Gitea, and Gerrit are not wired through this flow today. You can still publish branches and copy the URL out.
• PR review inside the app — once the PR exists, follow it up in your browser or in the gh CLI.
• Status checks / merge — there’s no merge button inside Glueprint; merge from GitHub or gh pr merge.

Mobile

The mobile app has a PR-creation modal too, with the same fields and the same gh requirement — on the host where the working directory lives, not on the phone.

Related topics

• Branches and tags
• Changes and commit