7 ms·
I use the GitHub Pull Request extension in VSCode to do the same thing (reviewing code locally in my editor). It works pretty well, and you can add/review comme
by hydroxideOH- 1y ago
I use the GitHub Pull Request extension in VSCode to do the same thing (reviewing code locally in my editor). It works pretty well, and you can add/review comments directly in the editor.
- cebert 1y agoI use this a lot too. Also, if you open a PR on the GitHub website and press the “.” key, it opens the review in VSCode, which I consider a much better web experience.
- reilly3000 1y agoTIL thanks.
- ivanjermakov 1y agoIt's better, but still quite deep vendor lock-in (in both GitHub and VSCode).
- hydroxideOH- 1y agoWell my employer chooses to use GitHub so I don’t have a choice there. And it’s vendor lock-in VSCode but that’s already my primary editor so it means there’s no need to learn another tool just for code review.
- NortySpock 1y agoGitHub may be dominant, but it's not like it doesn't have competitors nipping at its heels (GitLab, BitBucket come to mind). VSCode is open source, and there are plenty of IDEs... I guess I'm just focused on different lock-in concerns than you are.
- cyberax 1y agoJetBrains IDEs can do the same.
- plonq 1y agoUnfortunately it’s not feature complete - you can’t paste images in review comments, for example. Still very useful for large PRs though.
- deleted 1y ago[deleted]
- pm90 1y agoSame! Its much nicer now especially since Github seems to be pretty arbitrary/rigid about when it hides files that have "too many changes". Its so much nicer to see/navigate around such changes quickly in VSCode vs trying to do the same in the web interface. I suspect that since this is possible with VSCode/Github, its probably extensible to other providers editors.