spriha

This is great! Is there a limit to how often one can get property values reassessed? I'd pay for a service to automatically optimize my property taxes of it kept up with Zillow/redfin and auto-appealed each year that the market value was lower than the assessment.

Integration is as easy as clicking "install app" on your Github Repo :) though you'd still have to spend some time configuring rules on our settings page if you want to fine-tune advanced settings.

Re other companies: internal devX challenges that crop up while scaling eng teams seems to be a class of problems that isn't strictly CI or source control or deployment infra, though adjacent to a lot of such tools... Maybe that's why?

whoopsy! Thanks for the heads up!

Yes it can! we also have a search feature that lets you find PRs across repos (and by author, in case that's helpful)

I'd love to see the post on Premortems (never done one- what is it? Imagining how things could go wrong beforehand?) and Postmortems. Do post!

Make units like meters their own custom type for type safety - what a smart idea!

Haha yeah we're that company- turns out there's actually a lot to do, especially when handling this at scale! come join us :)

Fair point! We definitely don't want our analytics to be used to enforce/incentivize arbitrary targets (we've seen those behaviors backfire so many times, unfortunately...). I'll update the language from "Keep a tab on your builds and merges. Know your star developers" to "Keep tabs on your builds, merges and developer activity".

Thanks for the support!!

bors solves a similar problem, but we've found that enterprises require a lot of additional features to get their dev teams to actually use it, so we've focused on those to make this production-ready. Specifically:

1. We focus on being "no-maintenance", since our primary value prop to customers is "you won't have to spend eng resources on merge problems any more". This means: a one-click "set and forget" install, no additional config files to maintain or DSL to learn, unlike bors.

2. We have all the security and access-control features you'd want (we're Soc2 compliant, offer on-prem etc). This is important since the product interacts with our customers' source code.

3. We offer various customizations on merge workflows to help our customers optimize the exact parameters they care about (eg: developer wait time vs CI costs vs time to identity bad PRs in a batch, optimistic merge heuristics etc)

4. We offer a whole host of useful analytics to show you merge bottlenecks. We initially just put these as a nice-to-have, but we've now got customers who use us specifically because of these analytics!

We're also constantly adding new features based on customer requests (for instance, the flaky test features we're piloting originally came from customer requests we kept hearing over and over!). Speaking of which, if there's something you'd like to see that you don't currently get from your existing system/bors, do let me know :)