Skip to content

Add GitHub issue reporting flow to nullhub#12

Open
DonPrus wants to merge 14 commits intomainfrom
feat/report
Open

Add GitHub issue reporting flow to nullhub#12
DonPrus wants to merge 14 commits intomainfrom
feat/report

Conversation

@DonPrus
Copy link
Contributor

@DonPrus DonPrus commented Mar 18, 2026

Summary

  • add nullhub report with interactive and non-interactive issue creation for nullhub, nullclaw, nullboiler, nulltickets, and nullwatch
  • add /api/report plus a new /report UI flow with editable previews, structured bug/feature drafts, and system info prefill
  • preserve full manual fallback details when auto-submit fails, including repo, title, labels, real error messaging, and a prefilled GitHub issue URL

Verification

  • zig build test
  • zig build
  • npm --prefix ui run build
  • ./zig-out/bin/nullhub report --repo nullhub --type bug:behavior --message "Broken report flow" --dry-run
  • ./zig-out/bin/nullhub report --repo nullhub --type feature --message "Need better report drafts" --dry-run

DonPrus added 14 commits March 18, 2026 10:53
Defines the nullhub report feature: CLI command + Web UI + API for
creating GitHub issues with auto-collected system data across all
5 ecosystem repos, with gh/curl/fallback submission chain.
8-task plan covering CLI types, core module, interactive CLI,
API endpoints, Web UI page, label creation, and verification.
- report.zig: fix memory leaks in collectInstalledComponents and
  tryCurlCreate, add RFC 8259 control char escaping to writeJsonEscaped
- report_cli.zig: fix message and URL memory leaks, require --yes
  for non-TTY submission
- api/report.zig: add status field to error responses, add tests for
  invalid type, handleSubmit bad request, and repo mapping
- cli.zig: add exhaustive tests for toGithubRepo, displayName, issuePrefix
- +page.svelte: add clipboard fallback for non-secure contexts
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