4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c584dc57b9	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)	2026-10-26 18:37:02 +01:00
jschoubben	e1e5a8ff0d	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)	2026-10-26 18:34:03 +01:00
jschoubben	f0fbe193fa	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)	2026-10-26 17:59:34 +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