microsoft / microsoft/vscode-pull-request-github
Dismissing pull requests from the UI's tree
Open
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 working on a large code base the number of pull requests to walk through becomes unmanageable.
Ideally, one could take a work flow where they are presented "all open PRs" sorted by newest, and then "prune" this list to remove PRs which they are not interested in.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the pull-request tree UI and its data flow, then clarify how dismissed PRs should be stored and restored; done means users can prune the open-PR list without closing or changing the pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100