Skip to content
Zide Zide Zide

Pull requests

You can browse and filter pull requests for your GitHub repository from Pull Requests.

The line above the list says how many pull requests there are. With no filter conditions it says N pull requests. With any condition, the default open state included, it says N matches. Each condition shows as a chip above the count. To remove all of them, click Clear filters at the end of the count line. In a narrow panel the button says Clear. Warnings still explain incomplete data.

To open Pull Request, click DevOps > Pull Requests.

Pull requests are listed numerically and display the following information.

  • State badge: The badge that indicates if a pull request is open, closed, merged, or a draft.
  • Pull request number: The number of the pull request.
  • Pull request title: The title of the pull request.

The Pull Requests activity first lists enough pull requests to fill the panel, up to 30. Zide then reads the next page in the background, and more pages as you scroll toward the end of the list. Click Load more at the end of the list to read the next page at once. Reports and exports become available once every matching pull request is loaded.

When a project is shown, Zide reads this first page in the background, so Pull Requests shows it at once when you open it. Zide then reads the page again and updates the list only if it changed. Until that read is done, Load more is not available. If the read fails, the list keeps the pull requests it shows.

To open a pull request in a separate tab, right-click the pull request and click Open in New Tab.

Pull Request view

Click a pull request to open the pull request in the Pull Request view. Click Conversation, Checks, and Changes to change the displayed information of the Pull Request view. The view names show no counts. A ! next to a name means that Zide could not load that view, or loaded only part of it. When you return to the pull request with Back, the view that you left opens again.

Conversation view

You can view every comment and action of a pull request in the Conversation view. The Conversation view displays the pull request and the following information.

  • State: The status of the pull request, if the pull request is open or merged.
  • Milestone: The milestones associated with the pull request.
  • Assignees: The users assigned to the pull request.
  • Reviewers: The users assigned to review the pull request.
  • Labels: The labels attached to the pull request.
  • Project: The projects the pull request is a part of, each with its status. Zide reads and changes them with the account and host of the pull request’s Code Review source, not with the active account. The field shows Loading… until Zide has read the projects, then the project pills or None. Click the chevron to add the pull request to a project. Click a project pill to change its status or to remove the pull request from the project. If Zide cannot read the projects, the field shows Unavailable. Point to it to see the reason, for example that the account is not connected or that its token needs the read:project scope.
  • Linked issues: The issues linked to the pull request.
  • Changes: The amount of additions, deletions, and files changed in the pull request.

Click Commits under the metadata to see the commits in the pull request. Click a commit to open it. The button is dimmed when there are no commits.

Click the State pill to close or reopen a pull request, convert it to a draft, or mark it ready for review. The menu shows the actions available for its current state. A merged pull request cannot change state.

To move through a long conversation, use the minimap beside it. Blocks shows one mark for the description, each comment, and each review. Each mark reflects the length of its entry. Marks for approving reviews are green. Marks for reviews that request changes are amber. Point to a mark to preview the author and the start of the text. Click the mark to scroll to that entry. To show or hide the minimap, right-click the conversation or the minimap and choose Blocks or Hidden under Minimap.

Conversations start with Blocks. Your choice applies to every pull request and merge request conversation, and Zide keeps it after a restart. The Changes view has its own minimap, which follows your choice for diffs.

To copy text from the conversation or from a diff in Changes, select it, right-click on it, and click Copy. See Copy selected text.

Checks view

You can view the automated checks a pull request goes through in the Checks view. Each check indicates if the pull request passed or failed the check.

Click a check from GitHub Actions to open its workflow run in the Actions Run tab, with that check’s job open. A run in another repository, such as a fork, also opens there. See Runs from another repository.

A check that another service reports, such as a deployment preview, has a chevron at its left. Click the chevron or the check’s name to see which site reports the check and a button that opens the check on that site. You can open more than one of these checks at a time, and they stay open when the checks load again. A check without a details page cannot be clicked.

Changes view

Open Changes to view the changed files in a pull request. Use the dropdowns to filter by status or file type, or to show viewed, unviewed, or unavailable files. Type a file name in Filter files to find matching files.

Review comments on lines of a file show as threads under those lines. In the file list, a badge next to a file shows its number of unresolved threads.

  • To resolve a thread, click Resolve. The thread collapses and shows that it is resolved.
  • To open a resolved thread again, click Unresolve.

The button is dimmed until GitHub accepts the change. If GitHub rejects it, Zide shows the reason and loads the current state of the threads. Text that you typed in a Reply box and did not send stays.

Pull Request report

To open GitHub pull request reports, choose DevOps > PR Report and select a report from the Report Gallery. While a report is open, choose Change Report to select another report. Use the filter control to change the pull requests summarized by the report. For details, see Pull request report.

Create a new pull request

Use Generate in the Content header to draft the title and description with Zide. Its label stays visible when the fields contain text. Hover or focus the button to highlight both affected fields. Existing drafts open a review with selectable results, and applied results offer Undo. Review the content before creating the pull request.

To create a new pull request, complete the following steps.

  1. Click DevOps > New PR, or click New Pull Request in the Pull Requests activity.
  2. In the New PR tab, choose the Compare branch and the Base branch. Each field lists the local branches of the repository; type to search the list.
  3. In the Title field, enter the pull request name.
  4. Optional: Add labels, milestones, and assignees to the pull request in the Metadata section.
  5. Enter the pull request description in the Description field and click Create Pull Request.

A red asterisk (*) marks a required field. Create Pull Request is unavailable until both branch fields name local branches, the branches are different and have commits to propose, the Title field has text, and no attachment is uploading. Point to Create Pull Request to see the reason. If you leave the Title field empty, a message shows below it.

Zide pushes the compare branch to the remote that Git pushes it to, not to the repository that Code Review uses. When that remote is a fork of the repository, Zide creates the pull request from the fork. See Project header layout.

Filter pull requests

By default, the Pull Requests activity displays all open pull requests in a repository. Click the filter selector, the filter name after Filter:, to choose another filter. See Saved filters.

Click Show or hide filters to open the filter panel. It shows the common filters first: Search, State, Draft, Author, Reviewer, and Label. Click Advanced Options to show the other filters, in alphabetical order. Each tab remembers whether Advanced Options is open. You can combine filters: a pull request must match all of them. Press Ctrl+F (Cmd+F on macOS) to open the panel with focus on Search.

Each filter takes one value. Click a filter, then click a value. The value replaces the filter’s current value, and the list closes. The current value is highlighted. To remove the filter, click Clear at the bottom of the list, or click the x on its chip. To use several values or exclusions, see Several values and exclusions.

To search pull requests, click Search in the filter panel and type the words. Choose where to search, then press Enter or click Apply:

  • In titles, descriptions, and comments (the default) shows a Text chip.
  • In titles shows a Title chip.
  • In descriptions shows a Description chip.

In the default scope, GitHub shows the pull requests that contain all the words. Zide searches for each term as words: it puts quotation marks around a term such as label:bug or OR, so the term does not filter the list. To filter, use the filter buttons. In titles and In descriptions search for the words together as one phrase, so they cannot contain quotation marks; Zide removes them. A filter has one search, so a new search replaces the current one. Click the chip to change the words or where to search.

Pull request filters

  • Draft: Yes shows draft pull requests. No shows the pull requests that are ready for review.
  • Reviewed By: pull requests that a user reviewed.
  • Involves: pull requests that a user opened, is assigned to, commented on, or is mentioned in.
  • Mentions: pull requests that mention a user.
  • Commenter: pull requests that a user commented on.
  • Team Reviewer: pull requests that request a review from a team. Type the team as organization/team, for example zide-software/core. Apply is available when the value has this form.
  • Created, Updated, Merged, and Closed: the last 7, 30, or 90 days, this year, or more than one year ago. To use other dates, set From, To, or both, and click Apply. The range includes both dates. You can type a date, choose it from the calendar, or paste it in the form 2026-01-31 or 1/31/2026. To include closed and merged pull requests, set State to All first.
  • Comments: None, 1 or more, 5 or more, 10 or more, or 25 or more comments.
  • Linked Issue: Has linked issue shows pull requests linked to an issue that they close, for example with Closes #12 in the description. A pull request that only mentions an issue is not linked. Has no linked issue shows the others.
  • Project: pull requests in one of the repository’s GitHub projects. The chip shows the project name when the list of projects has loaded.

To find pull requests where a field is empty, open Assignee, Label, Milestone, or Project and choose No assignee, No labels, No milestone, or No project. To find pull requests where it is set, choose Has assignee, Has labels, Has milestone, or Has project. The choice replaces the other values of that filter. Click the chip to open its filter, or click Clear or the chip’s x to remove the condition.

Several values and exclusions

To use more than one value in a filter, or to hide pull requests that have a value, click Advanced Options and check Show Any / All / None. Then the Author, Reviewer, Reviewed By, Assignee, Involves, Mentions, Commenter, Label, Milestone, Base Branch, Source Branch, and CI Status filters show their values with two columns of checkboxes:

  • Any of: shows items that have at least one checked value. For labels, click the Any of heading to change it to All of. Then the list shows only items that have all the checked labels.
  • None of: hides items that have any checked value.

A value can be checked in one column only. The list updates after each change, and the list of values stays open. To show only the items with one value, click the name of that value. This clears the other checkboxes of that filter and closes the list. When you point at a name, the checkboxes show the result before you click. In long lists, such as labels, type in the search field to find a value. Click x in the field to clear the search. Click Done or press Escape to close the list. Clear removes all values of the filter.

To keep the exclusions, select the checkbox or round button beside Has …. This clears the named values but keeps the values under None of: Has labels with bug under None of shows labeled pull requests that are not bugs. Clicking the name Has … makes it the filter’s only condition, as clicking any name does. Choosing an included value replaces the No or Has condition, and choosing a value under None of keeps Has ….

Each filter shows as one chip, for example Label: bug or regression, not blocked. Click a chip to change its values. Click the x on a chip to remove the filter.

Point at Show Any / All / None to see which filters it changes: their borders change color. Other filters keep one value. Each tab remembers this setting.

If a filter has more than one value, or a value under None of, Show Any / All / None stays checked and is unavailable. The text below it names those filters, for example Keep at most one value and remove exclusions in Label to turn this off. This also happens when you choose a saved filter with such values. When those filters have at most one value and no exclusions, you can clear the checkbox. Clearing it does not change the filter or the list.

If you open a filter before its list has loaded, a line such as Loading labels… (or users, milestones, projects) shows in it until the list arrives. If you choose another remote for Code Review in DevOps > Configure…, the list and its filter choices reload for that repository. Your filters stay selected.

The Project list shows the open GitHub projects that are linked to the repository. If there are none, it says No open projects are linked to this repository. If Zide cannot read the projects, the list says why, for example that the GitHub token needs the read:project scope. Click Retry to read them again. When the cause is the account or its token, click Open Git Accounts to open Settings on Git Accounts.

Query text in older filters

A filter saved with Switch to Advanced Query in an earlier version of Zide keeps its query. Terms that the filters can show become their chips. For example, -label:docs shows as Label: not docs, -involves:octocat shows as Involves: not octocat, and label:bug OR label:ui shows as Label: bug or ui. Other query text, such as -draft:true, shows as one chip with a dashed border, and Zide still sends it to GitHub. To change that text, remove its chip. The Pull Requests list does not show a query field.

A term becomes a chip only when the filter can show all of it. Text in quotation marks stays as written: "label:bug" in:title is a title search, not a label filter. Saved title and full-text searches open as Title and Text chips of the Search filter. A date range such as created:2026-01-01..2026-01-31 becomes a Created chip. A term that a filter can show only in part, such as created:2026-01-01..*, stays whole in the dashed chip. The filter selects the same pull requests when you choose it again from Saved Filters or Recent.

Saved filters

Click the filter selector to see these groups:

  • Built-in Filters: filters that Zide provides: All PRs, Open PRs, My PRs, Needs Review, and Approved.
  • Saved Filters: filters that you saved for this project. Save Current Filter As… at the top of this group saves the current filters with a name that you enter, and selects the new saved filter.
  • Recent: filters that you used recently but did not save.

A check mark shows the selected built-in or saved filter. Ctrl+click (Cmd+click on macOS) a filter to open it in a new tab.

When you change a saved filter, the list updates at once, but the saved filter does not change. The selector shows the filter name followed by (modified), or an asterisk in a narrow panel. The filter list then starts with two items:

  • Save Changes saves your changes to the saved filter.
  • Discard Changes restores the saved filter and refreshes the list.

If you choose another filter without saving, Zide keeps your changes in Recent under the filter name followed by (modified). Recent keeps one such entry for each saved filter: newer unsaved changes replace the older ones. To keep a variant, save it with Save Current Filter As…. Choose the entry to continue: the saved filter opens with your changes, ready to save or discard. If the saved filter was deleted, the entry opens as an unsaved filter.

A filter that is not saved, such as a built-in filter that you changed, is named after its filters. Recent uses the same name.

To rename or delete a saved filter, click the More actions button (⋮) next to it in the list, then click Rename… or Delete…. These actions apply to that filter, also when you use another filter. Deleting a saved filter does not delete or change any pull requests. If you delete the filter that you use, the list changes to Open PRs.

In the list, the arrow keys move between filters, and Shift+F10 opens the More actions menu of a saved filter.

Saved filters belong to the project. The activity and the PR Report tab use the same saved filters. Issue filters are saved separately.

Assist with This

Right-click a pull request, or the tab of a Pull Request view, and point to Assist with This. You can also right-click the content header or an ordinary background area in the detail tab.

Under Zide Assist, click Add to Conversation to attach the pull request to a Zide Assist tab. You can also drag the pull request into a Zide Assist tab. For more information, see Attach items to a message.

Under Ask Zide, click Open Ask Zide. Zide opens the pull request in the Pull Request view with an Ask Zide panel beside it. In the panel, click Summarize Changes or Review Changes. Ask Zide does not post a review, approve, or merge. See Ask Zide beside a tab.

Check and pipeline status indicators use blue for running or queued work, amber when user action is needed, red for failures, and green for success. Cancelled, skipped, and unknown results are neutral.