{"version":"2.1.310","anchor":"runner-proxygoverned-git-validation-takes-new-inputs","canonical_anchor":"runner-proxygoverned-git-validation-takes-new-inputs","heading":"Self-hosted runner's pre-launch check gets more details about git and versions","tier":"internal","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/runner-proxygoverned-git-validation-takes-new-inputs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Self-hosted runner's pre-launch check gets more details about git and versions\n\nBefore launching a session, a self-hosted runner's config check now also learns whether git config is on and whether the launched program's version is known\n\n**Unclear.** What the check does differently with these new details.\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. Before it launches the program that runs a session, it checks its proxy and governed git setup. That check now receives:\n\n- the governed git setting as \"on\" or \"off\" instead of true or false\n\n- whether git configuration is turned on in the tool settings\n\n- whether the launched program's version is unknown, which is the case when that program is not the runner's own executable\n\n**Why**\n\nThe check may now accept or refuse some runner setups differently.\n\n- Area: Self-Hosted Runners\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}