feel free to ignore my nitpickings

On the contrary, I appreciate them 😆

@nstarman I changed the repo settings so that new commits won't dismiss review approvals anymore

Do you need me to squash and update the commit message?

Do you need me to squash and update the commit message?

nah there's a button for that

Hmm it requires signed commits, maybe we should disable that @nstarman ?

Or people should sign commits 😆

I'll sign and squash

(I added yaml to the main section since it was missing)

the commit isn't verified

Is something messed up with the code coverage check?

CI also fails on main, see #26

Thanks @NeilGirdhar !

I recently updated the wording of SPEC 8 to say:

It is also strongly recommended that release managers use signed commits, so that each release corresponds to a verified commit. Note that it can be difficult to enforce this via GitHub permissions without requiring all contributors to also sign their commits, which may be undesirable for many projects.

It used to recommend requiring signed commits via GitHub permissions, but we figured that this was untenable for array-api-extra given the current options available via GitHub.

noob question: what could go wrong if commits aren't signed?

other people can use your email in the Author field of a commit and it will look like it came from you. Unless your commits are always signed, in which case the commit will show as unverified (unless the other person has compromised your GPG keys or messed around in your GitHub security settings).