Forge rights read as the user sees them; write-only grant for mesh-tools; progress answers in minimal detail (issues 1945, 1947) #509

2026-10-26T20:07:16Z

mesh-tools commented

2026-10-26 20:07:16 +00:00

Issues 1945 and 1947.

gitea: a repository's effective permission is read as the user sees it (?sudo=), so gitea_unwritable_repos names what mesh-tools cannot write.
The operator's choice of 2026-10-26 18:30 ("Write, rule untouched"): mesh-tools gets write only; main's protection stays as it is except that mesh-tools is added to an enabled merge whitelist (ensureMergerListed); a merge it cannot make is reported (merge_blocked).
knowledge-base.progress answers detail: minimal (1947).

Quick fix: grant mesh-tools admin. Thorough fix (chosen, the operator's choice): write only plus a named merge whitelist, read and reported by tools.

Tried before the new one-check rule: try-1793040135267167865 passed at 21:02 CET (unit 2057 run, integration 2079 run). This pull request's check is its one run.

Reviewed-by: review-smalls@shanks at c584dc57b9

Issues 1945 and 1947. - gitea: a repository's effective permission is read as the user sees it (`?sudo=`), so `gitea_unwritable_repos` names what mesh-tools cannot write. - The operator's choice of 2026-10-26 18:30 ("Write, rule untouched"): mesh-tools gets write only; main's protection stays as it is except that mesh-tools is added to an enabled merge whitelist (`ensureMergerListed`); a merge it cannot make is reported (`merge_blocked`). - knowledge-base.progress answers `detail: minimal` (1947). Quick fix: grant mesh-tools admin. Thorough fix (chosen, the operator's choice): write only plus a named merge whitelist, read and reported by tools. Tried before the new one-check rule: try-1793040135267167865 passed at 21:02 CET (unit 2057 run, integration 2079 run). This pull request's check is its one run. Reviewed-by: review-smalls@shanks at c584dc57b95e52cfa7dc32bdeff20b0362a81de9

mesh-tools added 4 commits 2026-10-26 20:07:16 +00:00

gitea: mesh-tools administers a user's delivered repository and puts main's rule right, permissions read as the account sees them; knowledge-base.progress: minimal answers leave items to the tree, failed calls warn before parse faults (issues 1945, 1947) f0fbe193fa

gitea: main's rule read back must say what was written, since the forge silently drops a whitelist login that cannot write (issue 1945, review round 1) c85472285d

gitea: mesh-tools writes a user's delivered repository and main's rule stays the operator's: only its merge whitelist gets mesh-tools, read back; what else blocks the mesh's merge is said (issue 1945, the operator's answer 2026-10-26 18:30) e1e5a8ff0d

gitea: mesh/check is the mesh's own status and never blocks; signed commits, an outdated branch and a rejected review are said as blocking the mesh's merge (issue 1945, review round 2)

mesh/delivery merged: source.main moved to novox/mesh-catalog@3690c149c4ad

Details

mesh/check being carried to c584dc57b95e on 3690c149c4ad | a compiled program is not refused: mesh-build-node reported no programs

c584dc57b9

mesh-tools commented

2026-10-26 20:07:22 +00:00

Delivery novox/mesh-catalog@c584dc57b95e — merged since 2026-10-26T20:08:07Z

Source — source.main moved to novox/mesh-catalog@3690c149c4. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-26 20:07 (new) → proposed (announced): novox/mesh-catalog#509's head announced
2026-10-26 20:07 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-26 20:08 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@c584dc57b95e` — **merged** since 2026-10-26T20:08:07Z **Source** — source.main moved to novox/mesh-catalog@3690c149c4ad. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-26 20:07 (new) → proposed (announced): novox/mesh-catalog#509's head announced - 2026-10-26 20:07 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-26 20:08 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 3690c149c4 into main

2026-10-26 20:08:05 +00:00

mesh-tools deleted branch fix/progress-and-unwritable

2026-10-26 20:08:05 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#509