This message was deleted.
# how-do-i
s
This message was deleted.
p
you should be able to
stack submit
the whole thing!
j
Would that be the recommended/required workflow for me to
downstack get
and
stack submit
the whole thing now? I have been continuing to work off only my lower stack.. would doing it this way cause issues?
If I don't do
downstack get
on my coworker's branch, and instead I keep working on only my lower stack, then do
stack submit
only on the lower stack, then my coworker does
downstack get
, would it be able to pull in my updates from the lower stack and restack properly?
It would be difficult stay on up-to-date with coworker adding branches and constantly running
downstack get
to get the top-most branch from co-worker. Ideally if I'm working on the lower stack I would want to be able to continue working on that without worrying about child branches on top from collaborators.. wondering is that reasonable?
If anyone is interested, I'm able to work on the my part of the lower stack without needing to
downstack get
the branches that my worker is adding on top. If I submit changes to my lower stack, it may show up as diffs in coworker's PR. To fix that, coworker does
downstack get
to get my updates (overwriting the local branches assuming she didn't work on them), and then
upstack restack
and
upstack submit
from her bottom branch