{"version":"2.1.269","anchor":"self-hosted-runner-sessions-gain-session-git-rules-and-gh","canonical_anchor":"self-hosted-runner-sessions-gain-session-git-rules-and-gh","heading":"Self-hosted runner sessions gain 'session git rules' and gh route governance","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/self-hosted-runner-sessions-gain-session-git-rules-and-gh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Self-hosted runner sessions gain 'session git rules' and gh route governance\n\nSelf-hosted runner sessions now also reconcile 'session git rules' and a governed gh (GitHub CLI) route\n\n**What**\n\nBeyond rewriting git push URLs, self-hosted runner session setup now also reconciles a 'session git rules' file (checked against `git_mount_push_base_url`) and a governed `gh` (GitHub CLI) route with its own shim directory, both passed into the spawned session process. New telemetry events fire if the session fails to re-present its refreshed token for either of these.\n\n**Why**\n\nThis extends the governed-git relay mechanism to also cover git rules and GitHub CLI traffic, so both are subject to the same session-scoped credential control as git pushes.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}