Something went wrong. Try again.
atproto git client
Something went wrong. Try again.
fix(repo): refuse a configure that leaves another account's key pinned master
A failed push-key lookup was always a warning, so `repo configure --account B` against an unreachable PDS wrote B into `[user]`, left A's `core.sshCommand` in force and exited 0 — the next push authenticating as A while every commit said B. With nothing pinned the warning is still right; with a pin already there it is now a refusal that names the half-applied state, matching `clone --ssh`. Change-Id: I010a3c383fa7854b1d288efb90e933876da389cd
Author
permadeath.com Committer Tangled Date (Aug 27, 2026, 2:38 AM UTC) Commit 0bbd9b7c 0bbd9b7cc8115cfa49d5a9e8405a43d0ca72cc86 Parent 7e53a0f6 7e53a0f6b8bc933f4bf694b96112d8d7aff511f6