Skip to content

Conversation

@philips-software-forest-releaser
Copy link
Contributor

Note

Before merging this PR, please conduct a manual test checking basic functionality of the updated plug-ins. There are limited automated tests for the VS Code Extension updates.

Updates github.vscode-pull-request-github from 0.124.1 to 0.126.0

Release notes

0.126.0

Changes

  • A multi-diff editor can be opened for a pull request by URI. For example, vscode-insiders://github.vscode-pull-request-github/open-pull-request-changes?uri=https://www.github.com/microsoft/vscode-css-languageservice/pull/460.
  • There's an option to "Checkout on Codespace" from the pull request description webview.
  • ctrl/cmd + R when the pull request description webview is focused will refresh the webview.
  • You can "Reveal in Explorer" from files in the "Changes in Pull Request" view and the "Pull Requests" views.
  • Commit SHAs in PR file comments will be linkified.
  • Set "githubPullRequests.pullRequestDescription": "branchName" to have the pull request title pre-filled with the branch name when creating a new pull request.
  • The command "GitHub Issues: Open Issue on GitHub" can be used when your cursor is in an issue reference (e.g., #1234) in a text file to open the issue on GitHub.
  • Set "githubPullRequests.commentExpandState": "collapsePreexisting" to have pre-existing comments collapsed by default when opening a pull request description webview, while new comments remain expanded.
  • Choose which PR template to use when creating a new pull request (requires that "githubPullRequests.pullRequestDescription": "template" is set).

Button to change pull request template

  • Metadata from issue templates (e.g., assignees, labels) is now applied when creating a new issue from a template.
  • Issues created from TODO comments are assigned to the current user by default.
  • "githubPullRequests.createOnPublishBranch" can be set to "always" to always create a pull request when publishing a branch.
  • Open pull requests can be converted to drafts from the pull request description webview.

Convert to draft

  • We attempt to unwrap shortened commit lines in the pull request description webview to improve readability.
  • Copilot can generate descriptions for existing pull requests. "Edit" the description then use the sparkle icon to have Copilot generate a description.

Generate description for an existing pull request

  • Instead of checking out the default branch when you're done with a PR, you can configure that the PR base branch is checked out with "githubPullRequests.postDone": "checkoutPullRequestBaseBranch".
  • You can change the base branch of a PR from the pull request description webview.

Change base branch

  • PR branches can be configured to be automatically deleted when the PR is merged from this extension with the setting "githubPullRequests.deleteBranchAfterMerge": true.
  • When opening a folder for the first time, existing PR branches will be discovered and added to the "Local Pull Request Branches" view.

Fixes

0.124.0

Changes

  • The active pull request or issue webview title is now included as implicit context when using Copilot Chat. You can click on the implicit context item to include all the PR information in your prompt.

Pull request title as implicit context in Chat

  • Pull request and issue context can also be manually added to Chat from the "Add Context" menu.

Explicit Chat context

  • Single button for marking Copilot pull requests as ready for review, approved, and automerge (if enabled).

Single button to mark Copilot pull requests

  • The "Copy link" action for individual comments shows in the pull request description webview.
  • Comments that are part of an un-submitted review (only visible to you) now show with at "comment draft" icon in the editor gutter and in the Comments view.
  • For commits where checks have run, the commit status icon now shows next to each commit in the pull request description webview.

Fixes

Thank You

0.122.1

Fixes

0.122.0

Changes

  • Auto-generated PR descriptions (via githubPullRequests.pullRequestDescription) will respect the repository PR template if there is one.
  • Icons in the Pull Requests view now render with codicons instead of Unicode characters.
  • Drafts in the Pull Requests view now render in italics instead of having a [DRAFT] prefix.

Pull Requests view showing codicon labels and italic draft PR titles

  • Emoji completions for :smile: style emojis are now available in review comments.

Emoji completions in review comments

Markdown alerts in review comments

  • Opening an empty commit from a pull request webview shows an editor with a message instead of showing a notification.
  • Pull requests can be opened from from a url, for example: vscode-insiders://github.vscode-pull-request-github/checkout-pull-request?uri=https://www.github.com/microsoft/vscode-css-languageservice/pull/460
  • Icons are up-to-date with VS Code's latest icons.
  • If you start a review and want to cancel it, there's now a "Cancel Review" button in the pull request webview.

Cancel review button

Fixes

Thank You

0.120.2

Fixes

0.120.1

Fixes

0.120.0

Changes

  • The #openPullRequest tool recognizes open PR diffs and PR files as being the "open pull request".
  • All Copilot PR notifications can be marked as ready using the right-click context menu on the Copilot section header in the Pull Requests view.
  • The setting githubIssues.issueAvatarDisplay can be used to control whether the first assignee's avatar or the author's avatar is shown in the Issues view.
  • Instead of always running the pull request queries that back the Pull Requests view when refreshing, we now check to see if there are new PRs in the repo before running the queries. This should reduce API usage when there are no new PRs.
  • The "Copy link" action is back near the PR title in the pull request description webview.
  • You can configure that the default branch is pulled when you're "done" with a PR using "githubPullRequests.postDone": "checkoutDefaultBranchAndPull".

Fixes

0.118.2

Fixes

0.118.1

Fixes

0.118.0

Changes

  • There's a new code action "Delegate to coding agent" which shows on TODO comments. The "to do" keywords are configurable using the existing setting ``.

Todo comment with "delegate to coding agent" action

  • More of the new Copilot coding agent user entry points prompt for sign in if you aren't already signed in to GitHub (GitHub Copilot Coding Agent view in Chat Sessions, #copilotCodingAgent tool, "Delegate to coding agent" button).
  • Some of the individual extension views used the same icon, making it difficult to distinguish between them if you drag them into their own view container. To solve this, several views use a new icon: "Pull Requests" uses github-inverted, "Active Pull Request" tree view uses diff-multiple, "Active Pull Request" webview view uses code-review.
  • The "sidebar" content (reviewers, assignees, labels, etc.) in the pull request description webview have always moved above the pull request body when the webview width is narrow. Now, it also collapses into a compact, readonly view, which can be expanded to make modifications.

Collapsed sidbar content on a narrow view

  • Pull request and issue webviews restore after reload.
  • The new #openPullRequest tool in Copilot Chat lets you reference the pull request currently open in a webview. The #activePullRequest tool continues to reference the pull request currently checked out.
  • The "Edit Query" command in the "Pull Requests" view has an option to edit the query with Copilot.
  • Setting "githubPullRequests.ignoreSubmodules": true will cause the extension to ignore submodules when looking for pull requests.
  • In the "Issues" view, you can right click on an issue and "Assign to Coding Agent".

Fixes

Thank You

0.116.1

Fixes

0.116.0

Changes

  • #copilotCodingAgent renders the pull requests it creates as a PR card.

pull request card in chat

  • When checking out a Copilot-authored PR, the Chat view no longer opens.
  • You can dismiss the activity bar badge that indicates that Copilot has udpates to a PR by opening the PR description.
  • We've simplified the button bar on the pull request description.

simplified button bar in pull request header

pull request copy actions moved to link context menu

  • You can see a summary of the Copilot coding agent's status in the "Copilot on My Behalf" tree item

coding agent summary

  • The commit links in the pull request description will open in VS Code in the multidiff editor instead of going to GitHub.com.
  • The [WIP] prefix that Copilot adds to PR titles is no longer shown in the Pull Requests view.
  • Using @githubpr is now sticky and will be pre-populated into the chat input for subsequent messages.
  • Changes in a PR are pre-fetched when the PR description is opened.
  • Pull requested created by Copilot will have @copilot as placeholder text in comment inputs.
  • If your issue queries (setting githubIssues.queries) return no issues, a suggestion to configure your queries is offered.

suggestion in scm input to configure queries

  • The "Checkout Pull Request by Number" command will also accept a pull URL.

Fixes

0.114.3

Fixes

0.114.2

Fixes

0.114.1

0.114.0

Changes

  • We have expanded the integration with GitHub's Copilot coding agent (enablement instructions). You can see the status of all your Coding Agent pull requests in the "Pull Requests" view, and you'll get a badge indicating when a pull request from the Coding Agent has changes.

Pull Requests view with Copilot status

  • Links for viewing the Coding Agent session log now open within VS Code instead of opening in the browser.

Coding Agent Session Log

  • The #activePullRequest tool in Copilot chat now knows more about the active pull request: changes and Coding Agent session information. This tool is automatically attached to chat when opening a pull request created through the coding agent experience, so you can maintain the context and keep working on the pull request if needed to.

  • When checking out a pull request which doesn't have any diff from the parent branch, the pull request description will be opened, instead of the changes when "githubPullRequests.focusedMode" is set to "multiDiff" or "firstDiff".

  • You can start a new Coding Agent session by invoking the #copilotCodingAgent tool in chat. This tool automatically pushes pending changes to a remote branch and initiates a coding agent session from that branch along with the user's instruction. Experimental: Deeper UI integration can be enabled with the setting(githubPullRequests.codingAgent.uiIntegration) setting. Once enabled, a new Delegate to coding agent button appears in the Chat view for repositories that have the coding agent enabled.

Fixes

Thank You

0.112.0

Changes

  • Images in comments from private repositories are now shown in pull request file comments.
  • The "Notifications" view is now shown by default, collapsed.
  • Issue and pull request links in the timeline an in the issue/pull request body are now opened in VS Code, rather than going to the browser.
  • The "Assigned to Me" query in the "Pull Requests" view has been removed, and the "Local Pull Request Branches" and "All Open" queries can be removed using the setting githubPullRequests.queries. For repositories with Copilot, a "Copilot on My Behalf" query is added when the setting is unconfigured.
  • Unassigned events are now shown in the timeline.
  • Copilot "start working", "stop working", and "View Session" are now shown in the timeline.

Copilot start and stop working

Fixes

Thank You

0.110.0

Changes

  • In preparation for the release of Project Padawan, we added support for assigning to Copilot in the issue webview and [at]-mentioning Copilot in comments within files.
  • There's a new tool and context available in Copilot chat: #activePullRequest. This tool gives Copilot chat information about the pull request you have currently open in a webview (or checked out if no webview is open).

Ask Copilot to address the comments in the active pull request

  • The issue webview will show when an issue is opened from the "Issues" view or from the notifications view.

Issue webview

  • We revisited the top level actions in the Notifications view to make it cleaner, and aligned the display of the Pull Requests view and the Issues view so that they're more consistent.

  • There's a new warning before you try to create a pull request when there's already a pull request open for the same branch.

Warning shown when there's already a pull request for a branch

  • Pull Request webviews and issue webviews are refreshed every 60 seconds when they are the active tab.
  • The default action when adding a comment in a file is now to start a review rather than submit a single comment.
  • There's a new action on the Notifications view to mark all pull request notifications with "trivial" updates as done. Enable the action with githubPullRequests.experimental.notificationsMarkPullRequests.
  • Comment reactions are shown as readonly in the pull request webview (previously not shown at all).

Fixes

Thank You

0.108.0

Changes

  • Notifications in the experimental Notifications view can be marked as done.

Fixes

Thank You

0.106.0

Changes

  • You can provide custom instructions for GitHub Copilot when generating pull request titles and descriptions using the setting github.copilot.chat.pullRequestDescriptionGeneration.instructions. You can point the setting to a file in your workspace, or you can provide instructions inline in your settings:
{
  "github.copilot.chat.pullRequestDescriptionGeneration.instructions": [
    {
      "text": "Prefix every PR title with an emoji."
    },
  ],
}
  • We've added validation so that it's harder to accidentally set a github.com URL as the GitHub Enterprise URL.

Fixes

Thank You

0.104.1

Fixes

0.104.0

Changes

  • The Pull Requests view supports global queries. All old queries will be migrated when you open your workspace to include the current repo as part of the query. Global query support enables you to use the org and repo properties.
  • As part of the support for global queries, we also now have a today variable. This variable can be used to refer to the current day, or it can be used with a minus modifier. Together with the global query support, you can now make queries such as "my PRs in my work org that were created in the last 7 days":
    {
      "label": "My work last 7 days",
      "query": "org:microsoft author:${user} is:closed created:>=${today-7d}"
    }
  • The context menu in the Pull Requests view has been cleaned up.
  • The "pull request" icon shows in the the editor tab for the pull request descriptions.

Pull request icon in editor tab

  • :<emoji-name>: style emojis are now supported in comments.
  • You can now search with ctrl+f in the pull request description webview.
  • You can multi-select files in the "Changes in Pull Request" tree view and toggle the selected checkboxes with one click.
  • All non-outdated comments for a pull request will show in the "Comments" view when you open the pull-request's description, even if you don't have the PR checked out. They will hide again when all files related to the pull request are closed.
  • The "Changes in Pull Request" view has a shortcut for toggling editor commenting.

The eye icon as a shortcut to toggle off editor commenting

  • Python is no longer excluded from @ and # completions by default.
  • There's a new command to copy a pull request link: "Copy Pull Request Link".
  • git.showInlineOpenFileAction is now respected in the "Changes in Pull Request" view.
  • The "Resolve Conversation" and "Unresolve Conversation" command can now be used from keybindings.

Fixes

Thank You

0.102.0

Changes

  • The command GitHub Pull Requests: Close All Pull Request Editors will close all PR related diff editors and PR original file editors.
  • Summarizing a notification with Copilot will print a link to the issue in the Chat view.

Issue link shown in Copilot summary

Fixes

0.100.3

Fixes

Note: This breaks Enterprise 3.9 and earlier again.

0.100.1

Fixes

0.100.0

Changes

This month, our focus was on integrating Copilot into GitHub Pull Requests, using the new VS Code extension API, to showcase how Copilot can be added to an extension. These features are behind several settings. To try everything out, you can set the following settings:

  • "githubPullRequests.experimental.chat": true
  • "githubPullRequests.experimental.notificationsView": true

Copilot integration

  • The new @githubpr Chat Participant can search for issues on GitHub.

Copilot issue search for most open bugs in November

  • When displaying issues, @githubpr will show a markdown table and try to pick the best columns to show based on the search.

Copilot issue search for closed October bugs

  • Each issue listed in the "Issues" view has a new action, "Summarize With Copilot", that will reveal the Chat panel and summarize the selected issue. We also added another action, "Fix With Copilot", that will summarize the selected issue and will use the workspace context to suggest a fix for it.
  • We have added an experimental "Notifications" view that lists the user's unread notifications across repositories. By default the notifications are sorted by most recently updated descending, but you can use the "Sort by Priority using Copilot" action from the view title's ... menu to have Copilot prioritize the notifications. Clicking on each notification trigger an action to summarize the notification using Copilot. The view also contains easily accessible action to mark a notification as read, as well as open the notification on GitHub.com.

Fixes

0.98.0

Fixes

Thank You

0.96.0

Changes

  • Local changes to a checked-out PR can be quickly converted to suggestion comments from both the SCM view and from the diff editor context menu.

Convert local changes to suggestions

Fixes

Thank You

0.94.0

Changes

  • You can create revert PRs from the PR description. The PR branch doesn't need to be checked out to create a revert PR.

Create a revert PR

  • As a nice side effect of the enabling reverts, you can now see PRs whose branch has been deleted in the "Pull Requests" view.
  • The "Open Pull Request on GitHub.com" action shows even when there are PRs from multiple repos checked out.
  • img tags in code comments will now properly show the image for public repos.

Fixes

Thank You

0.92.0

Changes

  • Dates are listed in the "Commits" subtree for checked out PRs

    commits subtree with dates

Fixes

@philips-software-forest-releaser philips-software-forest-releaser bot requested a review from a team as a code owner January 18, 2026 03:14
@philips-software-forest-releaser philips-software-forest-releaser bot added dependencies Pull requests that update a dependency file vscode-extensions labels Jan 18, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 18, 2026

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 20 0 0 0.56s
✅ DOCKERFILE hadolint 2 0 0 0.78s
✅ GHERKIN gherkin-lint 6 0 0 2.39s
✅ JSON npm-package-json-lint yes no no 0.45s
✅ JSON prettier 19 4 0 0 0.44s
✅ JSON v8r 19 0 0 7.2s
✅ MARKDOWN markdownlint 11 0 0 0 0.94s
✅ MARKDOWN markdown-table-formatter 11 0 0 0 0.21s
✅ REPOSITORY checkov yes no no 18.67s
✅ REPOSITORY gitleaks yes no no 0.51s
✅ REPOSITORY git_diff yes no no 0.01s
✅ REPOSITORY grype yes no no 29.12s
✅ REPOSITORY secretlint yes no no 0.97s
✅ REPOSITORY syft yes no no 2.0s
✅ REPOSITORY trivy yes no no 5.74s
✅ REPOSITORY trivy-sbom yes no no 0.24s
✅ REPOSITORY trufflehog yes no no 2.31s
⚠️ SPELL lychee 77 2 0 57.52s
✅ YAML prettier 28 0 0 0 0.97s
✅ YAML v8r 28 0 0 8.14s
✅ YAML yamllint 28 0 0 0.88s

Detailed Issues

⚠️ SPELL / lychee - 2 errors
[IGNORED] docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a | Unsupported: Error creating request client: builder error for url (docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a)
[ERROR] https://www.conventionalcommits.org/en/v1.0.0/ | Network error: error sending request for url (https://www.conventionalcommits.org/en/v1.0.0/) Maybe a certificate error?
[ERROR] https://docs.sigstore.dev/cosign/signing/overview/ | Network error: error sending request for url (https://docs.sigstore.dev/cosign/signing/overview/) Maybe a certificate error?
[IGNORED] https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer | Unsupported: Error creating request client: builder error for url (vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer)
📝 Summary
---------------------
🔍 Total..........126
✅ Successful.....122
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........2

Errors in .github/CONTRIBUTING.md
[ERROR] https://www.conventionalcommits.org/en/v1.0.0/ | Network error: error sending request for url (https://www.conventionalcommits.org/en/v1.0.0/) Maybe a certificate error?

Errors in README.md
[ERROR] https://docs.sigstore.dev/cosign/signing/overview/ | Network error: error sending request for url (https://docs.sigstore.dev/cosign/signing/overview/) Maybe a certificate error?

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.3.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_HADOLINT,GHERKIN_GHERKIN_LINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security

@github-actions
Copy link
Contributor

github-actions bot commented Jan 18, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-rust:edgeghcr.io/philips-software/amp-devcontainer-rust:pr-1081

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 548.17 MB 548.17 MB +334 B (+0%) 🔼
linux/arm64 502.9 MB 502.91 MB +1.16 kB (+0%) 🔼

@github-actions
Copy link
Contributor

github-actions bot commented Jan 18, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:edgeghcr.io/philips-software/amp-devcontainer-cpp:pr-1081

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 683.37 MB 683.37 MB +241 B (+0%) 🔼
linux/arm64 665.29 MB 665.3 MB +536 B (+0%) 🔼

@github-actions
Copy link
Contributor

github-actions bot commented Jan 18, 2026

Test Results

 5 files  ±0   5 suites  ±0   5m 47s ⏱️ + 2m 9s
32 tests ±0  32 ✅ ±0  0 💤 ±0  0 ❌ ±0 
67 runs  ±0  67 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 38f2181. ± Comparison against base commit a3aa0b9.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link

@rjaegers rjaegers added this pull request to the merge queue Jan 20, 2026
Merged via the queue into main with commit f5056e1 Jan 20, 2026
35 checks passed
@rjaegers rjaegers deleted the feature/amp-devcontainer-cpp/update-vscode-extensions-devcontainer.json branch January 20, 2026 10:11
@github-actions
Copy link
Contributor

Pull Request Report (#1081)

Static measures

Description Value
Number of added lines 1
Number of deleted lines 1
Number of changed files 1
Number of commits 2
Number of reviews 1
Number of comments (w/o review comments) 5
Number of reviews that contains a comment to resolve 0
Number of reviews that requested a change from the author 0
Number of reviews that approved the Pull Request 1
Get the total number of participants of a Pull Request 5

Time related measures

Description Value
PR lead time (from creation to close of PR) 2.3 Days
Time that was spend on the branch before the PR was created 3 Sec
Time that was spend on the branch before the PR was merged 2.3 Days
Time to merge after last review 1.8 Hours

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 45 Min
Total time spend in last status check run on PR 15.6 Min

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file vscode-extensions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants