{"version":"2.1.271","anchor":"runner-session-host-config-apply-step-now-reports-partial-ap","canonical_anchor":"runner-session-host-config-apply-step-now-reports-partial-ap","heading":"Runner session host-config apply step now reports partial application and failures","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/runner-session-host-config-apply-step-now-reports-partial-ap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Runner session host-config apply step now reports partial application and failures\n\nCloud runner sessions now report when applying host git config partially fails or errors out\n\n**What**\n\nWhen a cloud or background runner session starts, it copies over your local git configuration (a \"host config apply\" step). This step now detects and reports more detail:\n\n- if the config could not be applied for a known reason, a notice is posted explaining why\n\n- if the apply only partially succeeds, a notice names the source directory it copied from and the error encountered\n\n- if the apply step throws an unexpected error, a \"host_config\" failure event is recorded before the error is passed along\n\n**Why**\n\nPreviously a failure in this step likely surfaced with less context. Now a partial or failed git config sync during a cloud session gives you a clearer reason why, instead of a silent or generic failure.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}