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

Offen
#3,504 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
github
Bereich
ai, authentication

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Go
Sterne
34.2k
Forks
5.3k
Ø Merge
5 T. 18 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/github-mcp-server

Alle Issues in github/github-mcp-server

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.