Hacker News new | ask | show | jobs
by brainwipe 571 days ago
The only one that directly annoys me is not being able to have threaded comments at the PR level. https://github.com/github/roadmap/issues/552 You can do it with "quoting", which is fine if there are two of you but turns into a mess if there's more than that.

They've said that they're watching the discussions for feedback, so I hope they listen and implement that one.

Happy that they are being transparent (rather than letting the issues rot), annoyed that they appear to be prioritising marginally useful AI stuff for basic UX.
2 comments
habosa 571 days ago
Shameless plug but this is one of the many GitHub code review limitations I set out to fix when I created CodeApprove (https://codeapprove.com).

You can comment on any line, a whole file, or a whole PR and all comments are threaded and tracked to resolution. They are never hidden because they’re outdated or because the discussion is too long.

link
dmazin 571 days ago
That is surprising to me. I am so tired of commenting on random lines with the usual "commenting on a random line for the sake of threading" apology.
link
progbits 571 days ago
Also commenting on random irrelevant changed line because you can't comment on unchanged ones (but they might need changes due to rest of the PR).

Github code review is horrible and I think it's actually worse than not having anything at all because now it's hard to convince people we should switch to something better. "Oh I don't want to learn another tool, github is good enough"

link
n4r9 570 days ago
> Also commenting on random irrelevant changed line because you can't comment on unchanged ones (but they might need changes due to rest of the PR).

Gitea does this as well, it's a real bugbear.

link