actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites
fix(docs-sync): the doctrine mirror is fetched from the forge in play, never a built-in one (#201)
@kimi-reviewer-andresmgsl @codex-reviewer-andresmgsl please re review this!!
docs/UPSTREAM-SYNC.md + .upstream-ref + the delta-inventory guard — the recurring sync, written from having just done one (#200)
lib/forge-*.sh + labels-reconcile — forge_commit_at, because Forgejo serves a single commit at /git/commits/{sha} (#209)
.pull_request == null, not has(), or this forge has no issues (#210)' (#211) from build/210-discriminator into main
issueflow-reconcile — the board discriminator is `.pull_request == null`, not `has()`, or this forge has no issues (#210)
lib/forge-forgejo.sh + labels-reconcile — label removal is a full-set PUT, and a write that did not happen fails the sweep (#192)
fix(docs-sync): the doctrine mirror is fetched from the forge in play, never a built-in one (#201)
same for @codex-reviewer-andresmgsl @glm-reviewer-andresmgsl , you are required as reviewers
fix(docs-sync): the doctrine mirror is fetched from the forge in play, never a built-in one (#201)
@kimi-reviewer-andresmgsl review again here please
a live forgejo-runner probe venue — every drill repo is archived, so the runner-only half of #192 has nowhere to run
Go with A per now.! Continue the word
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree, and port every gh call site it brought (#198)
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites
@cluade-reviewer-andresmgsl regarding 3, yes, fill a separate issue
actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree (10 files, 18 hunks) and port 0.6.0's new gh call sites
- Does the no-runtime-gh guard land here or in #200? = YES
- There is still no place to run a live forgejo-runner test, and no issue that owns one. = Lets keep this to later, create as an issue,…
.github/labels.conf + CONTRIBUTING.md — panel and triage name five identities that do not exist on this forge, so no issue can be normalized and no panel can converge
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer