You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(tree): handle redundant sequencing of local commit (#25544)
## Description
Fixes a bug in the scenario where a commit from a child shared branch is
concurrently merged into the main shared branch by different peers. The
peer whose merged commits are not sequenced first had a mistaken
expectation that it should have a commit on its main local branch for
each commit that is sequenced by the service if that commit came from
this peer. This is no longer a valid expectation.
## Breaking Changes
None
// This can happen if the commit came from a shared branch and was concurrently merged by another client.
910
+
// In this case, the newly sequenced commit is redundant and should therefore be ignored.
911
+
return;
912
+
}
913
+
907
914
// First, push the local commit to the trunk.
908
915
// We are mutating our `localCommits` cache here,but there is no need to actually change the `localBranch` itself because it will simply catch up later if/when it next rebases.
909
916
constfirstLocalCommit=this.localCommits.shift();
@@ -915,7 +922,6 @@ class SharedBranch<TEditor extends ChangeFamilyEditor, TChangeset> {
0 commit comments