Skip to content

File self-host feedback as GitHub issues - #104

Merged
shuv1337 merged 2 commits into
v2from
feat/feedback-github-issues
Nov 18, 2026
Merged

shuv1337 merged 2 commits into
v2from
feat/feedback-github-issues

Conversation

@shuv1337

Copy link
Copy Markdown
Owner

Summary

  • Self-host can file each feedback.submit submission as a GitHub issue: EXECUTOR_FEEDBACK_GITHUB_REPOSITORY (owner/repository) and EXECUTOR_FEEDBACK_GITHUB_TOKEN, with optional EXECUTOR_FEEDBACK_GITHUB_LABELS and EXECUTOR_FEEDBACK_GITHUB_API_URL (GitHub Enterprise Server).
  • The issue title is the message's first meaningful line (up to 120 characters). The body is the whole message, then sender, source, organization, instance and time.
  • With the operator webhook also set, the issue is filed first and the webhook payload gains issue: { url, number } and an Issue: <url> line in body. Feedback is accepted when either receiver took it, so a failed notification does not make a caller file the issue twice.
  • Same limits as the webhook: 10 seconds per receiver, redirects refused, nothing about the receiver in logs, traces or responses. No schema change. With neither receiver set, behavior is unchanged.

Verification

  • bun run check and actionlint .github/workflows/fork-ci.yml pass.
  • Named self-host scenarios pass (Node 24): the new self-host feedback files a GitHub issue and links it in the operator webhook, both feedback webhook scenarios, Hosted feedback enforces… and self-host with DO_NOT_TRACK….
  • The new scenario runs a fake GitHub API on a base URL with a path and covers: headers and token, title/body/labels, 422 and 307 refusal, both receivers, each receiver failing alone, both failing, a repository without a token, and token-free and URL-free server logs.
  • Mutation check: accepting feedback when GitHub alone fails made the scenario fail (expected 200 to be 503); restored.
  • Not run: the packaged-image (workerd) Docker scenario, which covers only the webhook, and a call against the real GitHub API. Both happen at deployment.

Deployment

Not deployed. Needs a fine-grained token with Issues read/write on the target repository, set on the host with the repository name.

feedback-github.spec.ts
feedback-webhook.spec.ts
feedback.spec.ts
instance-analytics.spec.ts

EXECUTOR_FEEDBACK_GITHUB_REPOSITORY and EXECUTOR_FEEDBACK_GITHUB_TOKEN file each
feedback.submit submission as an issue. With the operator webhook also set, the
issue is filed first, the webhook payload links it, and feedback is accepted when
either receiver took it.
@shuv1337
shuv1337 merged commit f482d19 into v2 Nov 18, 2026
4 checks passed
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.

1 participant