microsoft / microsoft/vscode-pull-request-github
Allow checking out the commits when reviewing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 796
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
If possible, I like to review PRs commits by commit. I d like to be able to check out these commits one by one, see what has changed and be able to comment on it and be able to edit them and try out some suggestions before proposing them.
Current behavior:
- commenting on separate commits doesn't work, (already opened an issue for that)
- can not make changes to the files
- without checking them out I cant see typescript types on hover etc.
Propose behavior:
- allow checking out the commit
- this would allow the files to be edited and have all vs code features
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 examining how the extension currently handles reviewing pull-request commits and why separate commits cannot be checked out or edited. Done means a reviewer can check out an individual commit, inspect TypeScript features such as hover information, edit files, and try suggestions before proposing them.
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
- 25/100