You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.271,
ImprovementsSection of the release
What
When 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:
if the config could not be applied for a known reason, a notice is posted explaining why
if the apply only partially succeeds, a notice names the source directory it copied from and the error encountered
if the apply step throws an unexpected error, a "host_config" failure event is recorded before the error is passed along
Why
Previously 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.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a stale .git/config.lock breaking git checkout -b, git push -u and git config for the rest of a session after a sandboxed command…
