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
Say I'm developing on branch feature1. I then start on feature2. I then go back and add a commit to feature1. feature2 isn't based on feature1 anymore, but a stray commit.
It'd be nice if we could "snap" feature2 to be based on the latest feature1.
The challenge will be in identifying which shared commits belong to which branch.
The text was updated successfully, but these errors were encountered:
This will help us avoid biasing our algorithms based on implementation,
like we could do with #6.
This involved an audit of different graph ops to see if this would have
an impact on them.
Auto-repair is starting off-by-default as we get runtime to see how well
we trust it.
Our backup approach in case aligning by time doesn't work is to prefer
HEAD.
Fixes#6
Say I'm developing on branch
feature1
. I then start onfeature2
. I then go back and add a commit tofeature1
.feature2
isn't based onfeature1
anymore, but a stray commit.It'd be nice if we could "snap"
feature2
to be based on the latestfeature1
.The challenge will be in identifying which shared commits belong to which branch.
The text was updated successfully, but these errors were encountered: