GitHub issues and pull requests

The GitHub tab lists the issues and pull requests of the project's GitHub repository. Open one to read it, see its checks, comment on it, hand it to an agent chat, and merge a pull request, without leaving Wrangl.

Before you start

Wrangl talks to GitHub through the GitHub CLI (gh) on the computer that runs Wrangl. It uses your gh login and never stores a token.

When the tab can't show the list yet, it tells you what to fix:

• GitHub CLI not installed: install gh from cli.github.com, then select Retry.
• This project isn't a GitHub repository: the project's Git remote is missing or points to a host the GitHub CLI doesn't know.
• Sign in to a host: select Sign in. Wrangl opens a terminal that runs the gh auth login command shown above the button. Finish the login there, then select Retry.

If your login is missing a scope, or GH_TOKEN or GITHUB_TOKEN is set and overrides your gh login, a yellow note appears above the list with the command that fixes it. Select the copy button next to the command and run it in a terminal.

Open the GitHub tab

Select the GitHub icon in the side panel. It is the fourth tab, after Changes. The list takes the place of the file list.

On a phone, open the side menu and tap the GitHub icon. See Use Wrangl on a phone.

Filter the list

• When the project is a fork, a Repository menu above the filters switches between your repository and its upstream.
• All, Issues and PRs pick the kind of item.
• The search field finds items by the words in them.
• State picks Open, Closed, Merged, Draft or All states.
• Labels shows items with any of the labels you pick, with all of them, or without them. The labels you filter by show as chips; select the x on a chip to remove it.
• The assignee menu picks Anyone, Assigned to me, Unassigned, Review requested (pull requests only) or Assigned to a person.
• Sort changes the order of the list.

On a phone, the label and assignee lists open as a sheet. Your choices apply when you select Done.

The list refreshes on its own every two minutes while Wrangl is visible. Select Refresh (the circular arrow at the end of the All, Issues and PRs row) to update it now. If a refresh fails, the last list stays on screen.

Each filter is kept per working copy, so a worktree can show a different list from the project folder.

Read an issue or pull request

Select an item to open it in a tab in the main area. The top of the tab shows the title, the state, and the Labels and Assignees rows. On a wide pane they move to a sidebar. The tab has these tabs:

• For a pull request: Conversation, Checks and Threads.
• For an issue: Conversation and Linked chats.

Conversation shows the description, the comments and events such as label changes, in one timeline. Comments from bots are folded to one line; select Show to read one. Checks lists failed, pending and cancelled checks first, and folds the rest behind Show N passed and skipped. A failed check has a log button that shows the last lines of its job log.

Open on GitHub opens the item in your web browser. To close an open item, select Close issue or Close pull request in its header. A closed issue has Reopen issue.

Edit labels and assignees

Select Labels or Assignees on an item to pick them from a list. Your choice applies when you select Done. To make a new label, type its name in the label list and select Create label. The list shows the labels with their GitHub colors.

On a wrangl-server that is read-only for remote clients, you can't change labels, assignees or the state of an item.

The tab stays open when you restart Wrangl, like other tabs.

Comment and reply

• To comment on an issue or pull request, type in the Leave a comment (Markdown) box at the bottom of Conversation. On a phone the box stays at the bottom of the screen, above the keyboard and select Comment. You can also press Ctrl+Enter (Cmd+Enter on macOS).
• To answer a review thread, select Reply under the thread, type your reply, and select Reply again.

The comment is posted on GitHub with your gh login, and the tab shows it as GitHub saved it. If GitHub refuses the comment, the error appears under the box and your text stays there so you can try again. On a wrangl-server that is read-only for remote clients, the comment and reply boxes are off.

Merge a pull request

The Merge section of a pull request has a merge method menu with Merge commit, Squash and merge and Rebase and merge.

• The merge button is on when GitHub says the pull request can merge now. Wrangl asks you to confirm before it merges, and the merge happens on GitHub.
• When the pull request can't merge yet, for example because checks are still running, select Enable auto-merge. GitHub then merges it when its requirements pass. Select Disable auto-merge to turn it off.

When you connect to a wrangl-server that is read-only for remote clients, the merge controls are off and show This server is read-only for remote clients.

Hand an issue or pull request to an agent

The buttons in the item's header start an agent chat with the issue or pull request already in the prompt. The chat uses the agent you picked last in the new chat launcher. If you haven't set up an agent yet, Wrangl shows Set up an agent first and opens the launcher.

For an issue:

• Start creates a new worktree from the project's default branch and opens a chat there with the issue as a prompt. The prompt is not sent yet, so you can edit it first.
• Ask opens a read-only chat where you can ask an agent about the issue. Every message in the chat tells the agent not to change files, commit or push.

For a pull request:

• Review opens a read-only chat where an agent reviews the pull request.
• Ask opens a read-only chat about the pull request.
• Fix CI appears when a check failed. It creates a new worktree with the pull request checked out and hands the failing checks, with the last lines of their logs, to an agent.
• Resolve comments appears when a review thread is unresolved. Pick the threads to hand off, then select Hand off. The agent works on them in a new worktree with the pull request checked out and can push there. You resolve the threads on GitHub yourself.

Fix CI and Resolve comments only appear on open and draft pull requests. When Wrangl can't let the agent push to the pull request's branch, for example a fork that doesn't allow edits from maintainers, the chat isn't started and a message says why.

Selecting Ask or Review again reopens the same chat. The Linked chats list on the item shows every chat started from it; select one to open it.

Buttons that create a worktree are off when the project isn't a Git repository, and when you connect to a wrangl-server that is read-only for remote clients.