Are Pull Requests Holding Back Your Team?

betterprogramming.pub

2 pointscodazoda3 comments

I'm curious about others who have tried this and how it went.

I've started several projects where I forgo the pull request process and things move really fast. Especially if I'm working through something alone and haven't involved a team yet. Once we get the first usable version out we'll typically start to think about the PR process, code reviews, deployment systems, and the like.

I'm curious how many of you simply trust the developers to work more directly on the system. Maybe some of you rely more on your tests to make sure things are smooth sailing.

I don't even trust myself, I like to set up PRs+integration test gates even when I am working solo.

That said, everyone pushing to trunk all the time is how we did stuff when we used subversion, so the sky won't fall. But I would miss being able to review changes and have async centralized tests, a lot.

Shameless plug: if your team uses Pull Requests but finds GitHub code reviews to be somewhat painful, I'm building https://codeapprove.com to solve your problems.

I think with the right tools and processes GitHub PRs are an amazing collaboration tool.

Reply on news.ycombinator.com