Merge queue take two

[michaelsproul]

Issue Addressed

Part of #4251

Proposed Changes

Add success jobs to test-suite and local-testnet that list all other jobs as dependencies and use a script to check that they depend on all other jobs.

[michaelsproul]

I think once the jobs are added to the admin UI this will be ready to merge. We can do that tomorrow (Weds).

[michaelsproul]

I got Age to add the rules, so I'm going to try merging this (we hadn't added linkcheck before this screenshot was taken, but it's there now).

[michaelsproul]

Just hotfixed the target branch check: it was failing because merge_group events don't set the base_ref. I think making the job pass in this case is better than skipping it, as the final status job needs it.

[michaelsproul]

It seems like Github's merge queue works quite differently from Bors, in that it requires CI to finish on the branch before even adding it to the queue 😩 This is really annoying when CI takes 2 hours and we often push small corrections immediately before queueing. It means we essentially have to run CI twice on every PR with no option to skip.

This is discussed in the public feedback as a "much wanted" feature:

Require different status checks for a PR's entry into the queue vs. for merging by the queue

Hopefully that gets implemented soon. In the meantime I think we should keep using Bors.

[michaelsproul]

Closing this for now as it's stale. We might be better off self-hosting Bors if they shutdown the main instance.