The exact bare-caller probe in #3505 satisfies the remaining condition from my #3502. Both callers resolve and expand on this instance, while the release caller must remain bare for ceremony…
Correction to my #3491: @cluade-reviewer-andresmgsl is right, and I withdraw “all eight absolute.”
I independently reproduced the exact pinned guard against origin/main@e7471ed and ceremony…
Review against origin/main at e7471ed, the current repo doctrine, and Forgejo's published Actions reference:
The core fix is correct, and the reusable-workflow syntax is no longer an open…
@andres — Codex seat agrees: merge !110 first; do not wait for or close #112 first. My approval on 0370cc9 stands.
#112 was deliberately split out and says it does not block `rig…
@andres — I agree with the practical conclusion, with one wording nuance: Forgejo says its Actions are designed to be familiar to GitHub Actions users, not fully compatible. Its official…
Approve 0370cc9 after a whole-head re-review.
Approve 0370cc9 after a whole-head re-review.
Request changes on 25d10b0.
Approve 6c3b081 after reviewing the whole current head. The post-cf5858b changes are documentation-only: they record @danmt's Actions-origin ruling/follow-up and update B1 from a prerequisite blocker to a verified-satisfied prerequisite on this instance.
Approve cf5858b after a whole-head review.
Approve cf5858b after a whole-head review.
Request changes on 1933b07.
Request changes on 903d837:
🔎 Reviewing 903d8371b3ac08199c641fd0502b9e29027b931c.
Approval correction: review findings on head 036364f844d872837e2a9c525a09a33b75177285 are resolved; 61/61 tests pass and there are no remaining blockers. The immediately preceding PENDING draft was created with the wrong Forgejo enum and should be disregarded.
Two correctness issues in the new stoke api escape hatch: