microsoft / microsoft/vscode-pull-request-github

[feature] mark/deprioritize generated files by default in Tree View

Open
#4,331 0 comments 1 reaction 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

When reviewing pull requests in GitHub web UI, it does a great job of collapsing/hiding generated content by default:

image

Users can do so by adding linguist-generated to these files .gitattributes as shown here: https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github

However, this experience does not translate well into VS Code, either from the desktop editor, or the www.github.dev UI.
I suggest graying out these entries as well in:

  1. The "Source Control" container (local changes tree view)
  2. The "Github Pull Request" container (active PR tree view)
  3. The active text editor file name (title).
  4. Possibly collapse these files/folder trees by default.

This seems to be possible via the new FileDecorationProvider VS Code API: https://code.visualstudio.com/api/references/vscode-api#FileDecorationProvider

This is especially important in projects that rely on code generation, where pull requests can contain a single file (source change), and many (tens) of other affected/generated files.

Any thoughts/suggestions welcomed.

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 with the FileDecorationProvider API and inspect the Source Control and GitHub Pull Request tree views, along with the active editor title behavior. Done means files marked linguist-generated are visually deprioritized in the requested surfaces; determine separately whether default tree collapsing is feasible.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, 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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.