External Pull Request Summary Page
  • 21 Apr 2023
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF

External Pull Request Summary Page

  • Dark
  • PDF

Article Summary

The External Pull Request Summary screen displays the list of pull requests that were created to date. Also, you have a provision to create a new pull request on this page.

Viewing the External Pull Request Summary Page

The External Pull Request screen is best viewed when the zoom setting is set to 75% on your chrome/firefox browser.
  1. Hover your mouse over the Version Control module and choose the option: External Pull Requests
  2. On the External Pull Requests screen, choose your repository and branch on which the pull request was initiated.
  3. Your newly pull request initiated will be displayed on the top with Open state including the list of added/ depreciated objects detail under the Commits tab.

It's always a good idea to break data into multiple pages when dealing with multiple pull requests records. You can browse 25, 50, 75, or 100 records on a single page, or you can navigate to the previous or next page using the Previous and Next buttons.

Create a new Pull Request

To create a new pull request, use the Create Pull Request button on the right side of the screen.

On the next pop-up screen, furnish the below details:

  1. Select your version control repository. Only those version control repositories for which the pull request is enabled will be listed under the Repositories drop-down.
  2. Choose the Source Branch and the Target Branch from the respective dropdowns.
  3. Give the pull request operation a Title and a brief Description.
  4. Add Reviewers that will accept your pull request. Optional Reviewer field will be displayed for repositories with Azure Cloud PRs supports.
  5. Select the Delete source branch after Pull Request closure to delete the branch once the pull request has been approved.
  6. Click OK to create a new pull request. The newly created pull request will get displayed on top of the list on the External Pull Request Summary page.

View the Pull Request difference

AutoRABIT compares the metadata between the Source Branch and the Target Branch and generates a metadata difference report. Such information can be viewed on the Diff screen. This screen will display the number of insertions and deletions to each metadata file. The lines highlighted in RED color indicate those are deleted in the Source Branch and for GREEN color indicates those are newly added in the Target Branch.

Diff UI for GitHub Pull Request 

Diff UI for Bitbucket Pull Request (provision to add/edit/reply comment for each line)

For the Bitbucket repo-enabled pull request, you have an option to add/ edit/ reply comments for each line of the code.

In a similar fashion, you will also be able to view/add/edit comments on the revision level (revisions under Commit sections).

Important Note:
  1. AutoRABIT supports inline add, edit, and replies comments for Bitbucket enabled pull requests only. This feature is currently not supported by GitHub.
  2. AutoRABIT synchronizes the pull requests to access the latest updates from the repository when clicked. Therefore, to show the latest changes, comments, or any updates, it is recommended to click on the individual pull request.
  3. The response includes a maximum of 300 files.

Additional Actions on Pull Request Page

1. More Operations

  1. Navigate to Pull Request Page: Clicking on the Pull Request label will take you to your GitHub/Bitbucket Pull Request page.
  2. Edit Pull Request: Modify the pull request information using the Edit () button.

2. Actions for the Pull request

After you create a pull request, you can ask a specific person to review your proposed changes. A reviewer has four possible statuses:

  • Approve: Submit feedback and approve merging the changes proposed in the pull request. Once the pull request is approved, the status changes to "Approved".
  • Decline: Reject the pull request
  • Merge: Merge the changes proposed in the pull request. Once the pull request is approved, the status changes to "Merged".
  • Reopen: Reopen the closed pull request again.

Was this article helpful?