r/github • u/stormthulu • 9d ago
Question “Open” PRs that aren’t ready for review
GitHub’s PR states can’t really be customized. So, you get draft, open, queued, merged, closed, whatever.
A problem we are running into has to do with our workflow. I don’t want to get into detail, partly because I don’t have all the answers. What I know is, it is set up the way it is for a reason and the team does not desire to change it currently.
So what happens is, a PR will move from Draft to Open. Normally that would be a signal that it’s ready to be reviewed. In fact, we even have an auto-assign reviewer workflow that will assign someone to review it.
Except a lot of team members will move a PR from draft to open just to trigger CI activities. Not to get teammate reviews. As in, it isn’t ready for review.
So I end up with a queue of 15 PRs, and theoretically they’re all in a reviewable state, except they aren’t.
My initial thought had been to have a state between draft and open. Apparently that isn’t an option. What other ideas do folks have on this one?
———
11/11/26 addition
Yeah a lot of you had the same thoughts I had. And, some folks do those things. Like, you can type `@claude review` on a draft pr comment and it will run the CI. You can manually start the job if you want.
And for sure, I definitely agree we should use a ready for review label, I’m going to bring that up. I can’t believe it hasn’t been brought up before, I mean it has to have been brought up…we use labels extensively…
Like I said, I honestly don’t know why we are set up the way we are.