3 ms·
Totally totally totally agree. I think a lot of the slow down comes from not understanding when the ball is in your court. And Github doesn't prioritize this b/
by tomasreimers 5y ago
Totally totally totally agree. I think a lot of the slow down comes from not understanding when the ball is in your court. And Github doesn't prioritize this b/c I think this problem is less prevalent in open source, where there is usually no expectation of a reasonable time until review.
A lot of what you described is exactly what we've built / we're planning for the code review portion of the site - you should sign up and check it out :)
- epage 5y agoGithub has been improving on this. I felt like they were rolling out the features I wanted right as I was enumerating them! They have - Auto-assign reviewers - Pings for people (unsure how sophisticated) - Auto-merge The review conversation itself is the big issue.
- SideburnsOfDoom 5y agoAgreed 100% Making it easier to stack PRs feels like entirely the wrong direction - "when you're in a hole, stop digging" - stacking is giving the people in the hole better shovels to keep digging with, instead of getting PRs flowing through more easily so that stacking is not needed so much.
- ahartmetz 5y ago"Stop digging" is not an option when working on a project that isn't entirely internal to one (sub)organization. These are not only open source projects.