{"version":"2.1.268","anchor":"push-on-release-message-clarifies-runner-side-credential-beh","canonical_anchor":"push-on-release-message-clarifies-runner-side-credential-beh","heading":"Push-on-release message clarifies runner-side credential behaviour and pushInsteadOf skip","tier":"notice","area":"Self-Hosted Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/push-on-release-message-clarifies-runner-side-credential-beh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Push-on-release message clarifies runner-side credential behaviour and pushInsteadOf skip\n\nPush-on-release failure message now explains credential and pushInsteadOf behavior more precisely\n\n**What**\n\nThe error message shown when a push-on-release fails for a governed git mount was reworded. It now says \"this runner-side push does not use the session's git-mount push URL,\" replacing older wording that described the governed mount as simply read-only. When a remote name is involved, the message now also explains that git skips every `url.*.pushInsteadOf` rule, including global and system-level ones, for this particular push, so the credential being used has to work on its own without relying on such a rule.\n\n**Why**\n\nThis gives a more accurate explanation of why a runner-side push might fail with credential errors, clarifying that push-URL rewriting rules don't apply and the credential must work unassisted.\n\n- Area: Self-Hosted Git\n- Names: `pushInsteadOf`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}