{"version":"2.1.280","anchor":"runner-sessions-can-now-apply-git-commit-signing-config","canonical_anchor":"runner-sessions-can-now-apply-git-commit-signing-config","heading":"Runner sessions keep git commit-signing config up to date","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/runner-sessions-can-now-apply-git-commit-signing-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Runner sessions keep git commit-signing config up to date\n\nBackground and cloud runner sessions now build and refresh git commit-signing config before running git-related hooks\n\n**What**\n\nWhen a background or cloud runner session starts, it now builds git commit-signing setup (signing artifacts) and applies it as git config so checkout and other git commands use the right signing settings automatically.\n\n- Session setup now generates signing artifacts and applies them as git config pins passed into the checkout hook, alongside the existing gh\/git config wiring.\n\n- Before running the post-session hook, the runner refreshes these session-scoped signing artifacts so the hook's git commands use up-to-date signing config.\n\n- If that refresh fails, the runner falls back to running the hook's git commands with commit signing turned off, and logs the reason.\n\n**Why**\n\nThis keeps git commits made during automated runner sessions properly signed without extra setup, and avoids silent failures by falling back safely (with a logged reason) if signing config can't be refreshed.\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}