Repository navigation
Conversation
People in trouble should not have to remember what to include, or start from a blank GitHub issue. /feedback asks for the diagnostic fields Linea already needs, files them as a structured issue, and the overlay's settings link opens that form with the current session filled in. Co-authored-by: Meet Bhatt <Meet2304@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Send on the site and in overlay settings POSTs to /api/feedback, which opens or comments on a GitHub issue. Crashes auto-send with signature grouping so a flapping renderer does not flood the tracker. Co-authored-by: Meet Bhatt <Meet2304@users.noreply.github.com>
The lede said “Send files it”, which does not read. Also give the too-short API error a period so it matches the form. Co-authored-by: Meet Bhatt <Meet2304@users.noreply.github.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
People hitting trouble should be able to send a sentence and have that become a GitHub issue you can close. Opening
issues/new(or copying a report) still asked them to have GitHub.Approach
POST /api/feedbackcreates a GitHub issue (or comments on an open crash with the same signature). The form is two chips — Problem / Idea — and one box. Linea attaches diagnostics in main; the renderer never talks to GitHub (default-src 'self').Crashes auto-send after renderer-gone, unresponsive, and uncaughtException. Same endpoint,
crashlabel. Local 1-hour dedupe plus a<!-- linea-crash:… -->marker so repeats comment on the open issue instead of opening a duplicate. GPU child-process blips are not sent.What this does
/feedback— Problem | Idea, one textarea, Send. Honeypot fieldcompany. Rate-limited by IP (5/10 min; Linea User-Agent 20/10 min).POST /api/feedback— files or comments on issues inMeet2304/Project-Linea. Response is{ ok: true }only (no issue number).LINEA_FEEDBACK_URLis set.Ops
Set
GITHUB_FEEDBACK_TOKENon Vercel (Issues: write on this repo). Falls back toGITHUB_TOKEN. Without a write token the form returns 503. The token stays server-side.How to try it
/feedback. Write a sentence, Send. With a write token it should appear on the Issues tab; locally without a token you should see “Reporting is not configured yet.”Verification
tsc+bun test lib+next build./api/feedbackreturns 400 / 200 (honeypot) / 503 (no token) as expected.