Thanks a lot!

No problem! It looks like this may have been meant to be merged. If so, auto-merge is still waiting on a review. (After it is merged, I'll rebase#1955 again.)

Thanks for the reminder! Apparently merges only happen after approval. However, I noticed that once approved, they can be merged even while CI is running. Probably becausemain isn't protected.

It sounds like protectingmain may be the way to go, so that approvals can be made either before or after CI finishes, without risk of inadvertently merging something that fails the tests. Is there any reason not to do that? Are there any changes to the workflows themselves that should be made to go along with or support it?

I took at look and it seems likemain is already protected, and as requirement for merging, an approval is set. What's also enabled is the need for checks to pass, but thanks to the worst UX, the checkbox does nothing. Instead, one has to pick each and every job individually, without a way to pick all at once.

This is where it stopped, again, and it's kind of where the famous auto-merge tends to stop for me 😅.

If I understand correctly, this is more manageable ingitoxide due toGitoxideLabs/gitoxide@943350a (GitoxideLabs/gitoxide#1551), plus the refinement inGitoxideLabs/gitoxide@4e672ef (GitoxideLabs/gitoxide#1668). Sometime soon, I can look into making a PR here with something like that.