microsoft / microsoft/vscode-pull-request-github

Open Github Action checks in Github Actions extension

Open
#8,600 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
TypeScript
Stars
2.6k
Forks
795
Avg merge
1d 4h
Merged PRs (30d)
46

Description

Feature Request

When viewing PR checks in the Pull Requests panel, the "Details" button currently opens the GitHub Actions run URL in the browser. It would be great if there was an option (or setting) to instead open the run in the GitHub Actions VS Code extension, keeping the workflow visible within the editor.

Motivation

Many developers already have the GitHub Actions extension installed alongside this one. Switching to the browser to view a workflow run breaks flow — especially when debugging a failing check and jumping between logs and code. A deep link to the Actions extension would keep everything in one place.

Suggested Behavior

When the GitHub Actions extension is installed, the checks "Details" button opens the run in that extension
When it's not installed, fall back to opening the browser (current behavior)
Optionally, a setting like githubPullRequests.checksOpenIn: "browser" | "actionsExtension" to let users choose

Related Issues
  • #4815 - GH-actions run overview
  • #5805 - Show workflow summary in UI

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Pull Requests panel at the checks "Details" button and trace how it currently opens the GitHub Actions run URL in a browser. Review the GitHub Actions VS Code extension's supported deep-link behavior and the related issues #4815 and #5805. Done means installed extensions can open the run in-editor, while the browser remains the fallback and any setting is honored.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.