Merge remote-tracking branch 'origin/main' into feat/r4g

2026-10-23 17:18:51 +02:00
parent b60077850d 3bec357968
commit b85d65b53f
13 changed files with 227 additions and 19 deletions
@@ -169,6 +169,12 @@
      "trusted": true,
      "default": {}
    },
+    "keep-main-rules": {
+      "type": "boolean",
+      "description": "Whether the module keeps main's branch protection as the mesh wants it. True: every ten minutes, and at the start, main's rule in every repository of the organisation novox is put to no push and the tools' account alone merging, and each apply of the `repositories` value narrows the main rule of the repositories it lists and swaps mesh/merge-gate for mesh/check in those it does not. False (the default): the module changes no existing repository's branch protection, whoever set it at the forge; a repository listed in `repositories` that does not exist is still made, with its first protection.",
+      "trusted": true,
+      "default": false
+    },
    "repositories": {
      "type": "object",
      "description": "The repositories of the organisation novox the mesh holds (ADR 0428): each by name, {\"<name>\": {\"private\": true, \"description\": \"...\"}}. One that does not exist is made by the module's setup login under its own account, its main protected and given a first commit (a README naming the description), its rule narrowed to no push and the tools' merge requiring mesh/check, and only then moved into the organisation; one that exists only has main's rule put right, mesh/check in place of mesh/merge-gate and mesh/repo-check and its other statuses kept (a main requiring mesh/repo-check alone keeps it). Every other repository whose main requires mesh/merge-gate has the two swapped for mesh/check; nothing else of a repository out of the value is touched.",
@@ -302,7 +308,8 @@
      "template": "files/config.json",
      "merge": "json",
      "takes-config": [
-        "url"
+        "url",
+        "keep-main-rules"
      ]
    },
    {