Insiders Feedback: GitHub MCP App retains completed issue creation form after submission

Offen
  • Stimmt etwas nicht?
#3,653 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
28/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
ai-infra-agents, frontend

Rechercherichtung

The payload names no files, functions or tests, so the first step is to reproduce it: ask the GitHub MCP App to create an issue, submit the form, then return to the same session. The issue does not show whether the form state lives in the MCP server (this repository, github-mcp-server) or in the Copilot host UI, so confirm that before looking for code. Done means the form is dismissed or cleared after a successful submission, and a reopened session does not show it again.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug insiders user-experience

Version: Insiders

Feature: GitHub MCP App

Feedback: After asking GitHub Copilot to create a GitHub Issue, the issue creation form appeared as expected with the generated issue details. I reviewed the information and clicked Create Issue, and the issue was successfully created.

However, after returning to the same session, the issue creation form appeared again, still displaying the previously generated issue details and waiting for a response to create the issue.

The issue creation functionality itself works perfectly, and I can continue interacting with Copilot normally, including sending new prompts. However, the previously completed issue creation form remains visible instead of being dismissed or cleared after successful submission.

I'm not entirely sure if this is an actual bug or an expected behavior, but I wanted to share this observation in case the form state is not being properly reset after a successful action.

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.