microsoft / microsoft/vscode-pull-request-github
Ability to filter PR commits by commit-hash range
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 796
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
On pull requests which are undergoing review, where the requestor has been attending to requested changes, it's really useful at GitHub.com to be able to filter by commit -- that is, to be able to view a ranged subset of commits for a PR so that only the latest changes can be observed to decide on approval for a PR which has undergone review and subsequent work.
At the moment, this would even be good enough through a command-palette interaction, for example, running the command "GitHub Pull Requests: Filter Current Request" and then getting a list of the commits, by hash (with the beginning of the commit message) in a list where one could ctrl-click or shift-click to select ranges of commits of interest, or just click to select a single commit of interest.
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
Start by reviewing the proposed “GitHub Pull Requests: Filter Current Request” command and how pull-request commits are presented in the extension. Define the selection behavior for individual commits and contiguous hash ranges, then verify that the resulting view shows only the selected changes for review.
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
- Mostly clear
- Newbie friendliness
- 35/100