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

Aperta
  • Qualcosa non va?
#3,653 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
ai-infra-agents, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
34.2k
Fork
5.3k
Merge medio
5g 18h
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/github-mcp-server

Tutte le issue di github/github-mcp-server

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.