atproto git client

fix(stack)!: refuse a link whose members share a commit master

A merge applies a member plus everything unmerged below it as one series, so two members carrying the same commit apply it twice — and that is what the order check required, since a `pr create` patch spans the target to its own branch. The check is on the patches now, where the merge looks. Change-Id: I35b40834d0819a535e4a9532cc8140867e9e15e1


+194 -1
4 changed files