The mesh writes the repositories it delivers, and asks no Approve for a merge it cannot carry out (issue 1945) #503

Merged

mesh-tools merged 2 commits from fix/forge-writes-delivered-repos into main 2026-10-26 16:25:07 +00:00

Conversation 1 Commits 2 Files Changed 17

+593 -11

2 Commits

Author	SHA1	Message	Date
jschoubben	24b244bc88	mesh-delivery-gate: ask no Approve of a merge the forge account cannot carry out, and say why (issue 1945) ... car-hunter #2 was approved and its commit status then refused 403. Before the ask the gate reads merge.writes for each repository it covers; where the merging account cannot write, nothing is asked, the delivery waits on 'the forge account cannot write <repo>: gitea_grant_write' and a condition is raised. gitea.repo.writable reads it again and asks an approved, refused merge of it again.	2026-10-26 16:39:56 +01:00
jschoubben	52de4c320e	gitea: the merging account writes every repository that builds a registered module, read from the indexer's modules (issue 1945) ... car-hunter #2 was approved and its commit status refused 403: mesh-tools only read the repositories of a user. It is now a write collaborator on each repository the indexer's modules state names (watched over the bus: at the start and on each registration), read back and said as gitea.repo.writable; the operator's other repositories stay read-only. gitea_grant_write and gitea_unwritable_repos do and show it by hand; gitea_commit_statuses answers merge.writes.	2026-10-26 16:36:50 +01:00