feat: issue-PR linking plugin to comment on issues when PRs reference them

[Copilot]

This PR implements a new plugin that automatically comments on issues when pull requests are created or edited to reference them. This addresses the long-standing request to help issue followers stay informed when discussion moves to a PR.

How it works

The plugin listens for pull_request.opened and pull_request.edited events and uses regex pattern matching to find issue references in PR titles. When it finds patterns like:

• "Fix Upgrade: [email protected] #123: resolve the bug"
• "Fixes #456 and closes #789"
• "Resolve Fix: commit-message failed on RFC refs #111, close chore: bump dependencies to address security vulnerabilities #222"

It automatically posts a friendly comment on the referenced issues:

👋 Hi! This issue is being addressed in pull request https://github.com/owner/repo/pull/456. Thanks, @contributor!

Safeguards against abuse

To prevent the abuse scenario mentioned in the original issue (PRs with titles like "#1 #2 #3 #4 #5 #6 #7 ..."), several safeguards are implemented:

1. Keyword requirement: Only recognizes issue references with proper keywords (fix, fixes, close, closes, resolve, resolves)
2. Maximum limit: Processes at most 3 issues per PR to prevent spam
3. Duplicate prevention: Won't comment multiple times on the same issue for the same PR
4. State checking: Only comments on open issues, skipping closed or non-existent ones
5. Graceful error handling: Continues processing if individual API calls fail

Implementation details

• New plugin: src/plugins/issue-pr-link/index.js
• Comprehensive tests: 8 test cases covering all scenarios in tests/plugins/issue-pr-link/index.js
• Integration: Added to plugin exports and enabled plugins list
• Code quality: Passes all linting rules and maintains existing test coverage

The regex pattern /(?:fix|fixes|close|closes|resolve|resolves)\s+#(\d+)/giu ensures that random issue numbers (like "#999 in documentation") won't trigger comments without proper context keywords.

Fixes #77.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

@nzakas 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.

[linux-foundation-easycla]

• ❌ - login: @Copilot / name: copilot-swe-agent[bot] . The commit (24be820, c05fa99) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[eslint-github-bot]

Hi @Copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @Copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @Copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @Copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @Copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[nzakas]

This actually looks like it should do what we want. Would like another review. @eslint/eslint-team

[eslint-github-bot]

Hi @copilot!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The length of the commit message must be less than or equal to 72

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here