This message was deleted.
# how-do-i
s
This message was deleted.
j
gt repo sync --restack
should rebase your stack for you — the merge conflicts here are not true conflicts
m
This is pretty non-intuitive, I still find myself having to manually resolve a lot of conflicts.
j
are these conflicts with your own changes or with other changes?
i would expect the latter but not the former
if you’re seeing the former, which CLI version are you on?
e
i would expect the latter but not the former
Are you saying this because you assume we get the "overwrite or rebase" prompt from the cli?
Because I experience this, conflicts with my own changes when restacking. In these cases, overwrite works great - no conflicts to resolve. But that only works if I know that I don't really have any unsubmitted local work (local changes, or commits that haven't been pushed yet)
The rebase option is what gets me in conflict hell
j
I'm only talking about
repo sync
at the moment, not
downstack get
we do have some improvements to
downstack get
planned that should alleviate the conflicts you're talking about here, but those are a slightly different issue from what it seems like Morgante is running into
e
Ah, I didn't realize my case is caused by
downstack get
, thought it was
repo sync
as well. Will pay attention next time I run them
m
I think these ended up being a weird mix of actual conflicts and my own code. I'll take a closer look next time.
s
IME you can run into weird conflicts if you have any merge commits in your stack. i would suggest never mixing rebase and merge strategies within the same stack.
👍 1
j
Yes, that's right! Thanks for flagging this @szaman — I had forgotten about that case