/feedback: “Save feedback bundle” is easily mistaken for submitting feedback
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
The /feedback flow presents an option labeled “Save feedback bundle.” This wording is easily interpreted as saving/submitting the feedback to GitHub, but the action only writes a local diagnostic archive. A user trying to send a complaint can complete the flow without realizing that nothing was transmitted.
Affected version
1.0.83
Steps to reproduce the behavior
- Run
/feedbackin Copilot CLI. - Choose Save feedback bundle.
- Observe that a local archive is created, but no feedback is submitted.
Expected behavior
Use an explicit label such as “Save diagnostic bundle locally” and clearly state that it does not submit feedback. Provide a separate, obvious “Submit feedback” action when direct submission is available.
Additional context
Linux, Copilot CLI 1.0.83. No session logs are attached because the wording problem is reproducible without them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /feedback flow in Copilot CLI and reproduce the listed steps. Update the “Save feedback bundle” wording and explanation to make the local-only behavior explicit, then verify that the flow still creates a local archive without implying that feedback was submitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100