Merging a PR with linking keywords no longer closing issues

[heaths]

Select Topic Area

Bug

Body

While some people actually want this behavior of not closing issues when using linking keywords like "fixes" or "resolves" (see #66741), my team uses it a lot. In the past couple of days, this hasn't been working. I had a couple of PRs with Fixes #123 or Resolves #456 in the PR description - not comments - and they were not closed.

The linking keyword is even underlined, but there's no longer a tooltip when you hover like there was before explaining what would happen. The issue also didn't have the PR linked.

One example: Azure/azure-sdk-for-rust#1812

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[dvg-p4]

For me, this happens sporadically and unpredictably: Sometimes Closes #123 will link the issue, sometimes it won't. Sometimes merging a PR with a linked issue will close the issue, sometimes it won't.

[Samoed]

The problem still occurs

[brandoncc]

I haven't had a problem with "Closes #123", but I just found that Closes #123, #456 only links the PR to issue 123. It should link to both.

[heaths]

FWIW, this is a documented restriction. You need to uses keywords for each separate issue: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#:~:text=octo%2Drepo%23100-,Multiple%20issues,-Use%20full%20syntax. AFAIK, this has always been the case.

If you want to try to change that with reasonable syntax like a comma delimiter, you might have better luck starting a new feature request (if there isn't one already).