🛠️ Repo: Detect and notify affected open PRs after merges

[mostafaNazari702]

Tooling Suggestion Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
• I have searched for related issues and issues with the faq label, but none matched my issue.
• I want to provide a PR to resolve this

Overview

I was thinking that merged PRs can sometimes affect other open PRs and issues by changing the same code, fixing bugs, or making parts of the codebase obsolete.

Maybe GitHub could detect when a merged PR overlaps with open PRs or issues and notify the affected contributors:

A merged PR changed parts of the code you are working on. Please check if it resolves your issue or if you need to rebase.

Now i am not sure if a similar idea can be applied to issues since it is not very easy for everyone to look into the codebase if a PR changed or addressed something related to their issue since one cannot say "I am guessing that the buggy code is in this file" and it won't be a good idea anyway because:

1, A lot of PRs get merged and it could get spammy in PRs but maybe we could make github actions first check if user first got a message in their issue/PR or not.
2, there are many old and open issues out there already that are from the original maintainers' time and those could also get flooded as well.

What do you guys think @mark-wiemer @JoshuaKGoldberg ?