GreenLane private preview

Help me validate the boring-PR auto-merge idea

My thesis is that developers spend too much time waiting for an approval or approving PRs that should obviously just merge. I also assume the problem is growing with AI-generated PR:s.

My app would would use plain old programming logic to classify PR:s based on the users settings to decide if it can me merged, approved or blocked.

About you & your team

Quick context so I can tell who the answer is coming from.

What's your role?

How many developers are on the team?

Which of these are in your codebase?

Ruby on Rails Elixir / Phoenix Other Ruby Other (not Ruby or Elixir)

Do PRs require at least one approval before they can be merged?

Do senior developers on your team spend too much time approving trivial or low-risk PRs?

Not at all A huge amount

Step 1 of 2

— Andreas Eriksson

This is me. I believe we need this in the world — to stop bogging down expensive senior engineers with PRs that any sensible rule could approve. Your honest answers decide whether I build it. Thanks for the few minutes.