{"version":"2.1.281","anchor":"runner-configure-git-refuses-to-run-governed-capacity1-se","canonical_anchor":"runner-configure-git-refuses-to-run-governed-capacity1-se","heading":"Runner --configure-git refuses to run governed capacity>1 sessions without commit signing","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/runner-configure-git-refuses-to-run-governed-capacity1-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Runner --configure-git refuses to run governed capacity>1 sessions without commit signing\n\nWith `--configure-git`, the runner stops governed sessions at capacity above 1 if commit signing cannot be set up\n\n**Unclear.** The finding does not define what a governed session is or what capacity counts.\n\n**What**\n\nFor governed sessions running at a capacity greater than 1, the runner's `--configure-git` setup now passes hook stubs to each session's config and writes commit-signing settings into that session's own git config file. Commit signing attaches a verifiable signature to each commit.\n\nThe session is stopped if:\n\n- the hook stubs are missing\n\n- the code-signing files are missing\n\n- writing the git config fails\n\n**Why**\n\nA session in this setup no longer runs on with unsigned commits when signing could not be prepared."}