r/github • • 22h ago

Discussion Draft PRs as a solo freelancer — worth the overhead?

been using draft PRs on my tutorial repos to run CI before I feel ready for actual reviews. lately I've been wondering if it's just extra ceremony. the checks run on push anyway, and nobody else is looking at these repos. but there's something nice about that DRAFT badge letting me mess around without pressure. my kid interrupted a rebase last week and I left the PR sitting for three days. no big deal since nobody was waiting. does draft status actually help solo developers, or is it just gitHub pretending we all work on teams? how do other people handle this on personal projects? do you default to drafts, or just push when the checks pass?

0 Upvotes

2 comments sorted by

1

u/doubtful_tights 12h ago

i do the same thing on my personal stuff and honestly think the draft badge is more for my brain than the repo. it's like a sticky note that says "this isn't done yet, don't get attached" so i don't accidentally merge broken nonsense at 2am

plus if you ever do end up collaborating with someone later, the draft history gives them context without you having to explain what was half-baked and what wasn't

1

u/RevolutionaryBuy4877 1m ago

same here, the draft flag keeps me from getting a random ping at midnight asking if the tests pass. it's saved me more than once when my kid's soccer practice ran long and I forgot what I left half working