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

Ouverte
#3,504 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
github
Domaine
ai, authentication

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
34.2k
Forks
5.3k
Merge moyen
5 j 18 h
PR mergées (30 j)
13

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/github-mcp-server

Toutes les issues de github/github-mcp-server

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.