Github sometimes closes issues that have been re-opened

When a commit contains the magic words Fixes #xxx, if that commit gets pushed to a repo by someone with permissions to close rust-lang issues, the issue will be closed. (I don't know the exact requirements, but it's something like this.) When a PR has these magic words in the PR description, that gets added to the merge commit message, and causes the same issue. This can lead to accidental issue closure when such a commit gets merged into our repo, then the issue gets reopened, and then the commit gets pushed somewhere.

I've seen this a few times over the last years. The most recent one is https://github.com/rust-lang/rust/issues/102048.

@rust-lang/infra is there anything we can do here? Like disable the "auto close based on commit message" feature (but keep it for PR descriptions!)? If not, maybe this could be added to the wishlist for the next meeting you have with Github people.

Start by reviewing the reported example in issue #102048 and the GitHub behavior described for commit messages, merged pull requests, and reopened issues. Determine whether repository settings can disable closure from commit messages while preserving PR-description behavior; done means documenting a confirmed configuration or the limitation and next action.