Auto-merge merges before CI finishes

[technicalpickles]

@josecolella and I saw this yesterday. It's a workflow we use during work of enabling auto-merge, so it will land when someone approves it.

Two places it didn't work as expected:

• ci: reorganize jobs, names, etc #38
• feat: Add client object #34

I think the fix is to make sure branch protections are on for requiring Status. While pairing with @josecolella on #34 we added the CI jobs, but unfortunately, the names have the ruby version encoded in them, which means it will change anytime Ruby version or the OS matrix changes.

In #38 I added a CI Status job that waits on everything else, which should do it. I think we just now need to updated to remove the old ones, and add CI Status to it.

Someone with admin on the repo would need to do that, as I don't currently have it.

[beeme1mr]

@technicalpickles I've updated the branch protection. I'll leave the issue open until I get confirmation that it worked.

[technicalpickles]

@beeme1mr hm, didn't quite work

It's looking for status but it's named like CI / CI Status. You might need to use the drop down thing to help select CI statuses in the last week (or whatever)

[beeme1mr]

Sorry, it should be working now.

[technicalpickles]

Looks better now, thanks!