Skip to content
Zide Zide Zide

Pull requests

You can browse and filter pull requests for your Bitbucket 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, merged, or declined.
  • 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.

When the pull request’s latest commit has a pipeline, a pipeline badge in the header shows its status. Click the badge to open the pipeline in its detail tab. For a pull request from a fork, Zide looks for the pipeline in the destination repository first, then in the fork. See Pipelines from another repository.

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, closed, or merged.
  • Reviewers: The users assigned to review the pull request.
  • Linked issues: The issues linked to 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 on an open pull request to open its close action. Bitbucket declines the pull request when you confirm. Declined pull requests cannot be reopened; create a new pull request from the branch to continue.

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

The Checks view shows the build statuses of the latest commit on the pull request’s source branch. These include Bitbucket Pipelines and other services that report to Bitbucket, such as Jenkins. The summary tells how many checks failed, are pending, stopped, or passed.

To open a check, click the chevron at its left or click its name. An open check shows which site reports it and a button that opens the check on that site. You can open more than one check at a time. A Bitbucket Pipelines check opens on Bitbucket. To see the pipeline in Zide, use Pipelines when the project’s automation source is configured for that repository. A check without a details page cannot be clicked.

When the source branch gets a new commit, the Checks view shows the statuses of that commit after the pull request refreshes.

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 or unviewed files. Type a file name in Filter files to find matching files.

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 who resolved it.
  • To open a resolved thread again, click Unresolve.

The button is dimmed until Bitbucket accepts the change. If Bitbucket rejects it, for example because someone already resolved or reopened the thread on bitbucket.org, 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. Threads that someone resolves on bitbucket.org show as resolved when you open the pull request again. Zide Assist can also list, resolve, and reopen threads.

Pull Request report

To open Bitbucket 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 Pull Request, 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 reviewers to the pull request in the Metadata section. Bitbucket pull requests do not have labels, milestones, or assignees. Zide does not load the pull request template from .bitbucket/pull_request_template.md.
  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. Zide cannot create a pull request from a fork yet. When the branch is pushed to a fork, the New PR tab says so, and Create Pull Request is unavailable. Click Create on Bitbucket to open Bitbucket’s create page from the fork to this repository. 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 State, Author, and Reviewer. 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 State.

Each filter takes one value. Click a filter, then click a value. The value replaces the filter’s current value, and the list closes. To remove the filter, click Clear at the bottom of the list, or click the x on its chip. Bitbucket cannot filter by several values or hide values, so Show Any / All / None under Advanced Options is unavailable.

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

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

Bitbucket shows the pull requests that contain the text in the place that you chose. Case does not matter. The words must be together as typed: login form does not find “Login to the form”. A filter has one search, so a new search replaces the current one. Click the chip to change the text or where to search. A search cannot contain quotation marks; Zide removes them.

Author and Reviewer

The lists in Author and Reviewer show the people on the 100 most recent pull requests of the repository. People who worked only on older pull requests are not in the lists.

Saved filters

Click the filter selector to see these groups:

  • Built-in Filters: filters that Zide provides: All PRs and Open PRs.
  • 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.