Incorrect user attribution in a task suggestion involving the GitHub MCP integration

オープン
#3,504 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
github
領域
ai, authentication

調査の方向性

The report does not name any file, test, or entry point, so the first step is to reproduce it: check which account the GitHub MCP tools authenticate as and how they resolve the authenticated user's comment history. Whether the cause sits in suggestion generation, session context, or the MCP server is unknown and needs a maintainer's guidance. Done would mean the origin of the misattribution is identified or a fix direction is agreed on.

索引モデルが issue の本文から書いたものです。

説明

bug

Description

While using ChatGPT with the GitHub MCP integration, I received an automatic suggestion to review [growthbook/growthbook#7309](https://github.com/growthbook/growthbook/pull/7309), a repository I do not recognize as related to my work.

The suggestion claimed that I had already replied “Fixed.” to a review comment at 19:38 UTC. However, verification through the GitHub MCP tools showed that the comment was written by a different account.

Verified evidence

The reply addressed a Cursor bot review requesting that a description be truncated to 80 characters. It was not posted by my authenticated account.

Actual behavior

The automatically suggested task presented another user's activity as my own and instructed the assistant to continue work on that PR.

The assistant began reading the repository through the GitHub MCP integration before I clarified that I did not recognize the task. No code changes or comments were submitted.

Expected behavior

  • Verify account identity before attributing GitHub activity to the user.
  • Explain why a repository or PR is relevant to a personalized suggestion.
  • Avoid presenting another account's comments as the authenticated user's history.

Investigation requested

Please investigate why this PR was suggested to my session and why activity by allileong was attributed to williambelini-maker.

The incorrect attribution is confirmed. Its technical origin is unknown: I cannot determine whether it originated in suggestion generation, context handling, or the GitHub MCP integration. This report does not establish a data leak or cross-account access.

主要言語
Go
スター
34.2k
フォーク
5.3k
平均マージ
5日 18時間
マージ済み PR(30日)
13

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/github-mcp-server のほかの issue

github/github-mcp-server の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。