105

I scanned the public repos of 128 YC-backed dev tools companies, 6,195 repos in total. I expected the companies building our tooling to enforce the basics on themselves. Only 2 of the 128 require any status check to pass before merging.

you are viewing a single comment's thread
view the rest of the comments
[-] eager_eagle@lemmy.world 8 points 1 day ago

IME some people (at least the ones who care) start more critical repos with good intentions, enabling most of these things.

But then comes a time where a hotfix must be merged asap to production and there's no one to review it for 3 days; branch protection gets disabled.

or an update in the code quality tooling detects an additional dozen warnings without the codebase changing; check enforcement gets disabled.

I think in most cases this is completely fine. Whoever is already a contributor should know what's the team policy merging things, and having ways to occasionally bypass these checks can be more beneficial than not.

this post was submitted on 30 May 2026
105 points (99.1% liked)

Programming

27108 readers
224 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS