Does disabling "Auto-close issues with merged linked pull requests" also disable explicit Closes/Fixes/Resolves keywords

[einaren]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

I’m seeing this behavior:

1. The repository setting "Auto-close issues with merged linked pull requests" is disabled.
2. A PR targets the default branch and includes an explicit closing keyword in the PR body, for example: "Closes #123".
3. The PR is merged.
4. The issue stays open.

This is surprising because I do not want all linked PRs to auto-close issues — that breaks workflows where one issue may have multiple PRs — but I would still expect an explicit keyword like Closes/Fixes/Resolves to close the issue.

This does not align with the docs: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

That page says a PR can be linked to an issue using a supported keyword, and that when the PR is merged into the default branch, the linked issue is automatically closed.

In my case, the PR still appears to have a closing issue reference, so the keyword seems to be parsed, but the final close step is skipped.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[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. ⭐

[ken-bouvet]

This behaviour also surprised me. But I also recognize that a product manager or task manager might be want to overrule the explicit closing as well.

I would propose to have this as a separate option -- expand the auto-close functionality to support keywords.