GitHub transaction safety · 2026 · Solo — trend research, GitHub transaction architecture, security hardening, interaction design, test-first implementation, production verification
Redline Repro
A guarded issue-to-test operator that binds one reviewed reproduction to an exact GitHub base before opening a draft pull request.
The problem
A maintainer can receive a precise bug report with a reproduction and desired regression test, yet turning that report into repository changes still creates authority, race, and untrusted-input risks. Redline Repro resolves one canonical public issue, verifies repository and pull-request identity, reviews one bounded test-only patch, and opens a draft pull request in a separate destination. It does not execute or merge repository code.
Architecture
Key decisions
Bind publication to what the operator reviewed
The browser cannot submit a replacement payload at publish time. A short-lived signed ticket binds the issue, destination, path, test content, base SHA, and branch; the server also requires exact-origin Fetch Metadata before any mutation.
Construct one inspectable Git transaction
Git Data API objects create a commit with an explicit parent after the source SHA is rechecked. Branch creation, draft-PR reuse, and compensating cleanup are idempotent and fail closed when identity or state drifts.
Isolate untrusted issue-authored code
The production golden path writes only to a separate private demo destination with GitHub Actions disabled. The application never runs the proposed test, never writes the source repository, and never grants itself merge authority.
Publish exact release evidence
Twenty-one unit tests, eight browser checks, English-only copy, lint, TypeScript, production build, independent review, and a real draft-PR golden path passed for functional SHA ec8baf03483f2352d3fd59053251ce681c22e7b5. Evidence SHA 3920cda90208d052f020e55825953694c96632bd received its own successful GitHub-to-Vercel production status.