feat: back link specs to their pull request#75
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
devloop | 3829f00 | Commit Preview URL Branch Preview URL |
Jun 22 2026, 01:36 PM |
Owner
Author
Devloop Review Round 1
Review 1Verdict: ACCEPT Acceptance matrix
Engineering quality matrix
Review flags
FindingsNone. Missing tests
Fix instructionsNone. Notes
|
Owner
Author
Devloop Final Report
Acceptance Matrix SummaryAcceptance matrix
Engineering Quality SummaryEngineering quality matrix
Implementation Summary
Commit References
Tests Run
Residual Risk
|
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.
Backlink specs to their pull request
Problem
Every spec carries a
pr: nullfrontmatter slot, anddevloopalready opens a draft PR and captures its URL in$PULL_REQUEST(devloop:2267), yet nothing ever writes that URL back into the spec. Sopr: nullstaysnullforever and there is no link from a spec to the PR that implemented it. The moment it hurts: revisiting a spec weeks later with no idea which PR (if any) shipped it, forcing a dig through devloop reports orgh pr listto reconnect the two.Outcome
After a successful
devloop <spec>run, the source spec file's frontmatterpr:field holds the full PR URL (e.g.pr: https://github.com/owner/repo/pull/123) instead ofpr: null, and every other byte of the spec is unchanged.Acceptance Criteria
AC1: After a
--create-prrun that opens PR URLU, the source spec's frontmatterpr:value equalsU(full URL) and no other line in the spec changes.AC2: Calling the helper when
pr:already equalsUleaves the file byte-for-byte identical (idempotent).AC3: A spec whose frontmatter lacks a
pr:line gains apr: Uline inside the frontmatter block; a spec with no closing frontmatter delimiter is left unchanged.AC4: A run invoked without
--create-prleaves the spec'spr:field unchanged.AC5: A failed backlink write (e.g. unwritable spec) does not change the run's exit status or final
STATUS.AC6:
bash scripts/devloop_test.shpasses, including a new test that covers the helper.Review Trail
Review rounds and the final report are posted as PR comments below.
Spec: .devloop/specs/2026-06-18-spec-pr-backlink.md
Generated by devloop.sh