{"version":"2.1.287","anchor":"self-hosted-runner-re-presents-full-remote-config-and-feeds","canonical_anchor":"self-hosted-runner-re-presents-full-remote-config-and-feeds","heading":"Self-hosted runners now pass the full \/remote setup to session git rules","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/self-hosted-runner-re-presents-full-remote-config-and-feeds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Self-hosted runners now pass the full `\/remote` setup to session git rules\n\nOn self-hosted runners, session token updates now use the whole `\/remote` setup and can add fetch rules for direct upstream repositories\n\n**Unclear.** It is not clear what the fetch lines do in a session.\n\n**What**\n\nOn a self-hosted runner, the step that refreshes a session's token now uses the whole `\/remote` setup. A self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. Before this change, the step used only the push address and the token.\n\nThe change matters where governed git has direct upstreams. Governed git is the setup that controls how a session reaches git repositories. Direct upstreams are repositories the session connects to directly. In that case, the runner now builds fetch lines from the listed sources. It passes them to the session's git rules together with the push address and the token.\n\n**Why**\n\nSessions on self-hosted runners with governed git can now have their fetch settings rewritten, as well as their push settings.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}