Add /newissue command to create follow-up issues from PR comments

[Copilot]

Implements a GitHub Actions workflow triggered by /newissue in PR comments to reduce manual overhead when tracking PR feedback items that should be deferred.

Implementation

Workflow: .github/workflows/create-issue-from-comment.yml

• Triggers on issue_comment.created for PRs only
• Validates commenter has write access
• Extracts content following /newissue command
• Creates issue with pr-followup label containing:
  • Comment content
  • PR context (title, URL)
  • Original comment link and author
• Posts issue link back to PR

Usage:

/newissue
Refactor error handling to use Result<T> pattern.
- Update method signatures
- Add integration tests

Creates issue titled: Follow-up from PR #456: [Original PR Title]

Pattern Consistency

Follows existing workflow patterns (fix-completions-on-comment.yml, update-xlf-on-comment.yml):

• Same authorization flow with permission checks
• Identical reaction-based UX (👀 → 👍/😕)
• Same actions/github-script@v7 action
• Consistent error handling and failure reporting

Deferred

Two-week reminder mechanism mentioned in issue requirements - would require scheduled workflow with state tracking, better suited as separate enhancement.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Migrate PR Comment to Issue</issue_title>
<issue_description>There should be a github actions workflow that contributors can trigger, such that when you type something such as /newissue, GH actions will file a new issue, and copy paste the quotes from the comment thread in a readable way, with a link to the discussed thread. The new issue will have a label to track these types, such as pr-followup. This is an interaction we often have, and while there is concern that making it easier to do this will discourage fixing feedback from PRs, sometimes we have nitpicks or other ideas that we may or may not want to do, and we'd rather not have to do the manual labor of making an issue and copying it over.

We could ping the individual who ran the command in 2 weeks to try to encourage followup on pending PR feedback items that were tracked this way. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Migrate PR Comment to Issue #52616

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[nagilson]

If it can resolve the comment thread and reply with the issue link that should also be done.

we should also only allow authorized contributors to run the workflow.

[nagilson]

may not be needed if GH added a similar feature