Prevent duplicate bot comments in auto-answer-issues workflow

[Copilot]

The auto-answer-issues workflow triggers on both opened and labeled events, causing the bot to post a new AI-generated comment every time a label is added to an eligible issue.

Changes proposed in this request

• Before calling Azure OpenAI or posting a comment, fetch all existing issue comments via octokit.paginate and check if github-actions[bot] has already commented
• If a prior bot comment is detected, log a message and exit early — no token consumption, no duplicate comment

const comments = await octokit.paginate(octokit.issues.listComments, {
  owner: REPO_OWNER,
  repo: REPO_NAME,
  issue_number: issueNumber,
  per_page: 100
});
const botAlreadyCommented = comments.some(
  (comment) => comment.user?.login === "github-actions[bot]"
);
if (botAlreadyCommented) {
  console.log("Bot has already commented on this issue. Skipping.");
  return;
}

Testing

No automated tests applicable for workflow logic. Behavior can be verified by triggering the workflow on an issue that already has a github-actions[bot] comment and confirming no new comment is posted.

Performance impact

Adds one paginated API call per workflow run before any OpenAI call. Negligible impact; saves cost on subsequent triggers by skipping the OpenAI call entirely.

Documentation

• All relevant documentation is updated.

---

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