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.

I'm focusing on the annual assessment appeal. So this you need to do every year. For me this year, for the first time, they kept the assessed value low.

Zillow and others don't use the right way to look at comparable homes in the assessors and assessment appeals board view.

I could auto appeal each year for you. Right now I'm just trying to get as many people to appeal before the deadline of Dec 1st for the remaining counties. But if you enter your address and email, then I'd run it next year and inform you.

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)

Hey HN! Ankit and I (from MergeQueue- YC S21) built Changesets to help coordinate Pull Requests across multiple repos.

If your team works on projects where developers have to submit Pull Requests across many repos, you've probably felt the pain of coordinating these groups of PRs so they all merge together without breaking dependencies. Github doesn't have a native solution to this, as it treats each repo as an isolated code base. With ChangeSets you can now group these PRs together so that they can be merged and rolled-back as a single unit of change.

If you’re on Github, we’d love to have you try it out! For now we’ve added ChangeSets as a toggle under our existing product (MergeQueue) since it was just lower overhead that way (email founders@mergequeue.com if you already have an account with us and we’ll let you into the ChangeSets beta), but you can sign up to try it directly using this link too: https://mergequeue.com/?ref=changesets

Let us know your thoughts!

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".

similar to how we compare with bors, actually! https://news.ycombinator.com/item?id=27858794

tl;dr: Our goal is to be the absolute lowest-maintenance option for your team :)