special keywords in PR does not work with sub-issues

[neeraj-ec]

Select Topic Area

Bug

Body

I am not sure if anyone else is facing this issue, after opting for Sub-issues public preview, I am facing two issues:

• Using special keywords like closes #<sub-issue number> does not automatically link sub-issue to the PR.
• If you manually link the sub-issue with PR, merging PR does not automatically close the sub-issue.

Here are steps which were working fine earlier and now not:

• Create a sub-issue under any issue.
• Create a new branch from the Issue page.
• Make some commits to the branch.
• Create a PR and in the body mention closes #<sub-issue number> special keyword.
  • This PR does not merge back to main branch. It merge back to some other branch of parent issue.
  • Mentioning special keyword in the PR body does not automatically link the sub-issue with the PR.
• You need to manually link the sub-issue to the PR.
• Merge the PR.
• Merging the PR does not close the sub-issue.

Earlier merging the PR used to close the issue automatically, now not.

Note

I have tried it in two separate repos. One which has sub-issues enabled and other one which does not have sub-issues enabled. This works fine in the repo with no access to sub-issues, linking using special keywords and auto closing issue when PR is merged.

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