feat(pr): replace per-round comments with one living review status - #101
Merged
Merged
Conversation
Every pass previously appended a full review dump, and the run appended a final report on top, so a four-pass run buried the reader under five walls of text. The PR now carries exactly one status comment, found by a marker and edited in place. The comment leads with the current state, a two-row quality gate table, and open findings. Review history, gate matrices, the full review, and run details move into collapsed sections, so a human sees the verdict first and opens only what they need.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
devloop | 4ef5ad9 | Commit Preview URL Branch Preview URL |
Aug 17 2026, 07:47 AM |
The fake gh now stores the marked comment and answers gh api PATCH, so the loop tests prove a two-pass run creates exactly one comment, edits it on the later pass, and keeps one history row per pass.
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
1 participant
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.
Why
Each review pass appended a new comment containing a full dump of the review file, and the end of the run appended a final report on top. A four-pass run buried the reader under five walls of text with no summary, so a human opening the PR had to read everything to find the verdict.
What
How
<!-- devloop-review-status -->identifies the comment.find_status_commentextracts the REST comment id from the comment URL andupsert_status_commentPATCHes it throughgh api, falling back to creating one when none exists.--edit-lastwas deliberately avoided because it targets the author's last comment, which may be a human's.States follow the run:
Review pending,Changes required,Review unavailable,Final verification,Ready for human review. The last two come from the readiness gate in the parent PR.Pass history is appended to
.devloop/status/<slug>-history.tsvand rendered as a table inside a collapsed block, so earlier rows are never rewritten..devloop/status/is registered as a runtime artifact so it is never committed.The full review stays available in a collapsed
Latest review detailblock, which is also whatlatest_pr_review_commentreads when a run resumes and local review files are gone.Proof
bash scripts/devloop_test.sh: passes, except the same pre-existingnightshift digestsandbox failure present onmain.ghfailure paths.Scope
Stack
feat/sha-bound-acceptancefeat/stacked-pr-manifests