Skip to content

fix: route feedback submissions through Issues API to resolve timeout errors#1

Open
Sriram2272 wants to merge 1 commit into
mainfrom
fix/feedback-submission-timeout
Open

fix: route feedback submissions through Issues API to resolve timeout errors#1
Sriram2272 wants to merge 1 commit into
mainfrom
fix/feedback-submission-timeout

Conversation

@Sriram2272
Copy link
Copy Markdown
Owner

Problem

Reported by @jav099 in github#52 — users on v0.2.2 (macOS) receive a "Submission timed out" error when clicking the Submit feedback button in the bottom-left of the UI.

Root cause

.github/commands/feedback.yml had surfaces: [discussion], which routes in-app feedback submissions to the GitHub Discussions API. The Discussions endpoint is significantly slower than the Issues API and more susceptible to connection timeouts, especially on slower or high-latency networks.

Fix

Switch the surfaces field from discussion to issue:

 surfaces:
-  - discussion
+  - issue

This aligns with what was described in the v0.2.3 release notes:

"The feedback form now shows a notice that submissions will be posted as public GitHub issues, and the submit button is labeled 'Share feedback'."

The Issues API is faster, more reliable, and the right target for this type of structured user feedback.

Template cleanup

The previous template body included several paragraphs of instructional preamble that were discussion-specific (references to first-session video recordings, multi-day onboarding cadence, etc.). These no longer apply in an issue context and added unnecessary payload to each submission. The six core feedback questions are preserved — only the surrounding prose is trimmed.

Testing

  • Feedback submissions no longer hit the Discussions API, eliminating the timeout path
  • The six structured questions remain intact for product team use
  • The template renders cleanly as a GitHub issue body

Closes github#52

… errors

The feedback command was configured with `surfaces: [discussion]`, which
routes submissions to the GitHub Discussions API. This endpoint is slower
and more prone to connection timeouts, causing users to see "Submission
timed out" errors when submitting in-app feedback (reported in github#52).

Switching the surface to `issue` uses the Issues API, which is faster and
more reliable for this type of user-submitted content. This aligns with
the intent described in the v0.2.3 changelog, where the feedback form was
updated to post submissions as public GitHub issues.

The template is also tightened — the previous version included several
paragraphs of instructional preamble that added unnecessary payload size
and referenced discussion-specific conventions (video threads, multi-day
cadence) that no longer apply in an issue context.

Fixes github#52
Copilot AI review requested due to automatic review settings May 15, 2026 02:02
@Sriram2272 Sriram2272 self-assigned this May 15, 2026
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Switches the in-app feedback command from the Discussions surface to the Issues surface to resolve submission timeouts reported in v0.2.2, and trims the feedback template's discussion-specific preamble while preserving the six core questions.

Changes:

  • Change surfaces from discussion to issue in .github/commands/feedback.yml.
  • Remove discussion-specific instructional preamble (first-session video, multi-day cadence) from the template.
  • Preserve the six structured feedback questions and add brief HTML comment hints.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Submit feedback button not working

2 participants