from Hacker News

Ask HN: Have you found a good workflow for reviewing PRs on GitHub?

by soenkeliebau on 4/28/21, 3:00 PM with 6 comments

I am beginning to despair. I can't even really put my finger on what exactly it is, but I find reviewing PRs on github extremely painful. For example, I keep missing my own comments when checking back if the author addressed them. Why is there no list of "all my comments"? Maybe filterable by outdated,resolved and open..

  • by codeapprove on 4/28/21, 8:15 PM

    I’m building a much better tool for reviewing code on GitHub. Still in early stages and looking for feedback, but our central idea is exactly what you mention. We make sure that all comments are resolved before the review is done and help you focus on what needs resolution.

    Check out https://codeapprove.com or just email me at sam@habosa.com if you’re interested

  • by naivebull on 4/28/21, 3:17 PM

    I do code review on both Gitlab and Github and found the experience on Github more pleasant. Things that help:

    - Keep the PR small, the code changes focused.

    - The “viewed” checkbox per file. Tick it as the file is reviewed. If the file is changed later, it will expand as “Changed since last viewed”. If not, one less thing to check on next review iteration.

    - Keep discussions off Github. There should be one comment per issue as the initializer as well as reminder. The long discussions goes into a Slack thread.

    - The reviewer is the one to resolve the comment. This way, you can resolve them as in “tick them off” as done.

  • by piotrkaminski on 4/29/21, 12:37 AM

    <plug> You might want to check out Reviewable (https://reviewable.io) if you haven't yet. It addresses your complaints about comments on GitHub and many more besides, while remaining as integrated with GitHub as feasible. Some pretty large open source organizations are using it, e.g. CockroachDB. </plug>