docs(MIRRORING): the PR bridge exists and is unscheduled, and it is gh/<n> with the GitHub title #1681

Merged
jaylouisw merged 1 commit from docs/1116-1515 into main 2026-11-16 15:22:03 +00:00
Owner

docs/MIRRORING.md �2 described the PR bridge as unbuilt, and described a different bot than the one in the tree.

Against scripts/gh-bridge.js (in the tree since #1074):

  • branch is gh/<n> (script:270), not gh-pr/<n> as the step list said;
  • the Forgejo PR keeps the GitHub title verbatim (script:277) � there is no [gh#<n>] prefix;
  • the body carries the original description, a credit line, the head SHA and the <!-- gh-pr: <n> --> marker (script:287-299);
  • idempotence is keyed on that marker (script:260-263), not on the head SHA;
  • the merge comment reads Merged on the forge as <url> (commit <sha>) (script:343), not Landed as <url>;
  • there is no update or close path at all, so a force-push or a close on GitHub leaves the Forgejo PR alone.

What is genuinely missing is the job: no file in .forgejo/workflows/ invokes the script. The status note now says written-and-unscheduled rather than not-built, and CONTRIBUTING.md no longer calls the crossing automatic.

Gates: syntax-check 352 files OK, docs-show-commands 7/7, help-completeness 8/8, doc-catalog-counts 43/43, control bytes clean, citations exit 0, canonical URLs OK (2843 files). Docs only.

`docs/MIRRORING.md` �2 described the PR bridge as unbuilt, and described a different bot than the one in the tree. Against `scripts/gh-bridge.js` (in the tree since #1074): - branch is `gh/<n>` (script:270), not `gh-pr/<n>` as the step list said; - the Forgejo PR keeps the GitHub title verbatim (script:277) � there is no `[gh#<n>]` prefix; - the body carries the original description, a credit line, the head SHA and the `<!-- gh-pr: <n> -->` marker (script:287-299); - idempotence is keyed on that marker (script:260-263), not on the head SHA; - the merge comment reads `Merged on the forge as <url> (commit <sha>)` (script:343), not `Landed as <url>`; - there is no update or close path at all, so a force-push or a close on GitHub leaves the Forgejo PR alone. What is genuinely missing is the job: no file in `.forgejo/workflows/` invokes the script. The status note now says written-and-unscheduled rather than not-built, and `CONTRIBUTING.md` no longer calls the crossing automatic. Gates: syntax-check 352 files OK, docs-show-commands 7/7, help-completeness 8/8, doc-catalog-counts 43/43, control bytes clean, citations exit 0, canonical URLs OK (2843 files). Docs only.
docs(MIRRORING): the PR bridge is written and unscheduled, and it uses gh/<n> with the GitHub title
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 25s
CI / Docker build (pull_request) Successful in 35s
CI / Test (Node 18) (pull_request) Successful in 1m11s
CI / Test (Node 20) (pull_request) Successful in 1m19s
CI / Test (Node 22) (pull_request) Successful in 1m30s
d85d4fab03
Section 2 described a bot that did not exist yet, and described it wrongly: the branch is `gh/<n>` not `gh-pr/<n>`, the Forgejo PR keeps the GitHub title instead of gaining a `[gh#n]` prefix, idempotence is keyed on the `<!-- gh-pr: N -->` marker rather than the head SHA, there is no update or close path, and the merge comment reads "Merged on the forge as ..." not "Landed as ...".

scripts/gh-bridge.js has been in the tree since #1074 with --issues/--prs/--report/--all/--dry-run/--limit, so "not built yet" was stale; what is genuinely missing is a job, since nothing in .forgejo/workflows invokes it. CONTRIBUTING.md said the crossing was automatic, which contradicted that.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 15:21:50 +00:00
jaylouisw force-pushed docs/1116-1515 from d85d4fab03
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 25s
CI / Docker build (pull_request) Successful in 35s
CI / Test (Node 18) (pull_request) Successful in 1m11s
CI / Test (Node 20) (pull_request) Successful in 1m19s
CI / Test (Node 22) (pull_request) Successful in 1m30s
to becf482d1a
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
2026-11-16 15:21:53 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1681
No description provided.