Cross-linking regression: editing in an issue or PR reference now usually has no effect

[EliahKagan]

Select Topic Area

Bug

Feature Area

Issues

Body

When an issue or pull request contains a reference to another issue or pull request, whether as a full URL or as a short reference such as #123, the linked-to issue or pull request shows a link back. But recently this appears to be broken. When the reference is edited in later, cross-linking does not occur. It used to occur for edited-in references, but that seems to have stopped happening sometime in the last week or so. This applies both to initial posts that are later edited, and to subsequent comments that are later edited.

Occasionally editing in a reference still triggers cross-linking, but I have only been able to get it to happen when the reference is added in an edit made just a few seconds after the post being edited was first posted.

I've tested this in EliahKagan/hello-world#31, EliahKagan/hello-world#32, and EliahKagan/hello-world#33, where, for example, EliahKagan/hello-world#33 contains an edited-in reference to EliahKagan/hello-world#32, which has no event linking back.

I can provide "natural" examples where this appears to have happened if desired, but I've omitted that for now since it could be more distracting than illuminating. I have primarily observed this in issues and their comments, but also in pull requests and their comments, which I believe are equally affected. (Discussions are of course unaffected because they intentionally do not participate in automatic cross-linking.)

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

[EliahKagan]

The problem seems to have gone away.