snap-issue-github-inline-screenshot
ARCHIVED“Propose the next step in that browser extension such that images are stored in the github issue as well as locally.”
STAGES
- proposal05-21
- requirements05-21
- design05-21predates the Figma as-is + proposed pair
- tasks05-21
- build—
- archived—
CAPABILITIES — 2 IN ONE CHANGE
- snap-issue-github-config1 requirement
- snap-issue-github-screenshot-embedding4 requirements
OUTCOMES — AND HOW EACH IS MEASURED
- ✓1.1User can submit a valid capture and obtain a GitHub HTTPS image URL suitable for Markdown without manually opening github.com to upload the crop (when credentials meet documented scopes).not stated
- ✓1.2User can open the new issue in a fresh session and see the screenshot rendered inline, not only a “Local file (Downloads)” line.not stated
- ✓1.3User still receives the cropped `snap-issue-*.png` in Downloads after a successful submit, with local-save behavior unchanged.not stated
- ✓1.4User sees a clear, actionable error if GitHub rejects the upload or a follow-up body/comment update fails, without a false “success” state.not stated
- ✓1.5User can read required GitHub token scopes and any new `host_permissions` / API hosts in the extension README.not stated
- ✓1.6User still gets a GitHub issue whose title and body include Capture, Note, and Follow-up sections as defined for Snap Issue.not stated
- ✓1.7User gets both the local PNG artifact and an inline GitHub-hosted image on the same successful submit path.not stated
- ✓1.8User sees a readable GitHub API error when issue creation fails (for example 401, 403, 404, or validation).not stated
WHAT HAPPENED
- TASKS
proposal and specs and design and tasks landed
2026-05-21 · 1 pull request- #168chore(openspec): archive merged hub and snap-issue changes
History read from a manifest built at 2026-09-30 (09e7bcc).
1 pull request, found by commits touching the change folder