e236318647
Merge pull request 'lib/forge-forgejo.sh + labels-reconcile — label removal is a full-set PUT, and a write that did not happen fails the sweep (#192)' (#206) from build/192-label-write into main
a35a77f752
fix(forgejo): a read failure names its verb too, and the tests assert the whole diagnostic (#192)
062e016a42
fix(labels): all four review gaps — preserved ids, zero-write no-op, every mutation counted, no success token (#192)
0f20f4b6ef
fix(labels): a label removal that cannot happen fails the sweep, and removal itself now works (#192)
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
790c4d226f
Merge pull request 'actions/* + lib/* + CHANGELOG — merge upstream 0.6.0 onto the forge tree, and port every gh call site it brought (#198)' (#204) from build/198-upstream-0.6.0 into main
adf907c963
fix(198): the action fails closed, the caller decides scheduling, the guard decides the forge (#198)
97e63acef0
fix(refs-not-closing): report and skip on a forge it cannot speak, rather than reddening every PR (#198)
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
dad99ddfb9
Merge pull request 'labels.conf + CONTRIBUTING — the panel and triage rosters name identities that exist on this forge (#195)' (#196) from build/195-roster-mapping into main
labels.conf + CONTRIBUTING — the panel and triage rosters name identities that exist on this forge (#195)
forge_label_remove — every label removal on Forgejo returns HTTP 500, and labels-reconcile reports it as reconciled
go with codex recommendation.. approving YES; continue with the development.
forge_label_remove — every label removal on Forgejo returns HTTP 500, and labels-reconcile reports it as reconciled
Can any of you explain me in a TLDR the @kimi-reviewer-andresmgsl question for me?? an also, add any other question pending.
lib/facts.sh + release.yml — the release doors are gh-only, so neither can publish on a Forgejo consumer
I need you to solve this @cluade-reviewer-andresmgsl , what @codex-reviewer-andresmgsl said
forge_label_remove — every label removal on Forgejo returns HTTP 500, and labels-reconcile reports it as reconciled
my bad, #192 is open, i was wrong. Please continue