How to Use Rider’s Built‑In Pull Request Tool Window for GitHub, GitLab, Bitbucket, and Azure DevOps
Enable and use JetBrains Rider’s Pull Request tool window in minutes. Configure OAuth tokens, view and merge PRs, and avoid common pitfalls.
05 Jan 2026, 20:03 UTC

Why Use Rider’s Pull Request Tool Window?
JetBrains Rider ships a dedicated Pull Request (PR) tool window that lets you browse, review, and even merge PRs directly from the IDE. You can connect to GitHub, GitLab, Bitbucket Server, and Azure DevOps without leaving Rider, reducing context switches and speeding up the review workflow.
Prerequisites
- Project must be a Git checkout with a remote URL that exposes a REST API (e.g., https://github.com/… or https://dev.azure.com/…).
- Rider’s Git plugin must be enabled (File → Settings → Plugins → Installed → Git).
- Valid OAuth or Personal Access Token (PAT) configured in File → Settings → Version Control → GitHub (or GitLab, Bitbucket, Azure DevOps).
- User must have permission to read and merge PRs on the target repository.
Step‑by‑Step Configuration
- Add an OAuth token for GitHub (the process is similar for other providers):
- Navigate to File → Settings → Version Control → GitHub.
- Click Add account and choose Log in via OAuth.
- Rider opens a browser, you grant access, and a token is stored automatically.
- Alternatively, paste a PAT and check Activate.
- Verify that the account appears in the list and is marked as active.
- Open the Pull Request tool window:
- Go to VCS → Git → Pull Requests (or press
Ctrl+Alt+Pon Windows/Linux,⌘+Alt+Pon macOS). - The window will display a list of open PRs for the current repository.
- Go to VCS → Git → Pull Requests (or press
- Review a PR:
- Double‑click a PR entry to open the diff view.
- The diff shows added and removed lines, the PR title, author, and status.
- Merge or Close a PR:
- In the diff view, click Merge to perform a fast‑forward or merge commit via the provider’s API.
- Click Close to close without merging.
- Refresh the list:
- Click the Refresh button (circular arrow) or press
Ctrl+Rto pull new PR data from the remote.
- Click the Refresh button (circular arrow) or press
Example Configuration Snapshot
Below is a textual representation of the Settings dialog for GitHub. Replace YOUR_TOKEN with your actual PAT.
File → Settings → Version Control → GitHub
Accounts:
• GitHub – [contact removed] (active)
• Token: ************ (hidden)
Limitations & Common Mistakes
- No Inline Comments in Diff View: Rider’s PR window shows the diff but does not support adding inline comments. Use the web UI or a third‑party plugin for that feature.
- Stale PR List: The tool window does not auto‑refresh on its own. Remember to click Refresh after new PRs are opened.
- Token Expiration: OAuth tokens expire after a set period. If the PR list becomes empty or merge actions fail, re‑authenticate.
- Missing Remote URL: Local or bare repositories without a remote URL will not show PRs. Ensure
git remote -vlists a valid remote. - Incorrect Provider Settings: Using the wrong provider (e.g., configuring GitHub when the repo is on GitLab) will result in an empty list. Verify the provider matches the remote URL.
Verification Checklist
- Open Rider and navigate to VCS → Git → Pull Requests. A list of open PRs should appear.
- Double‑click a PR. The diff view should load and display changes.
- Check that the Merge button is enabled only if you have merge rights.
- In Settings → Version Control → GitHub, confirm that a token is present and marked as active.
- Trigger a Refresh and observe that new PRs appear.
Practical Tips
- Use a dedicated PAT with only the
reposcope for GitHub to limit permissions. - Enable Automatic Pull in
File → Settings → Version Control → Gitto keep the local branch up‑to‑date with PR branches. - Keep the Git plugin up to date; newer releases include bug fixes for the PR integration.
Conclusion
Rider’s Pull Request tool window is a lightweight, integrated way to manage PRs without leaving the IDE. By configuring OAuth tokens, ensuring the repository has a remote, and refreshing the view regularly, you can review and merge PRs efficiently. Remember the limitations—especially the lack of inline commenting—and supplement with the provider’s web UI when needed.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.