-
(hidden) S7heV0oEv #[[(hidden) S-ygYfi0j]]
-
(hidden) 035gpJQ0W
-
(hidden) cRIXYfuB4
-
(hidden) 4n5dvwbHU
-
[[git-stacked-rebase]]
-
{{[[TODO]]}} usage w/ #[[(hidden) gpwvvVB_X]] is annoying because the expected node version that #[[(hidden) qbhpV9DHv]] was built for might differ
-
{{[[TODO]]}} `break` before `branchEnd` -- looks like the branchEnd gets lost because break itself doesn't have a commit SHA
-
{{[[TODO]]}} will need extra care here - i think i mentioned before, but if you break right before the branch end, & create new commits, then those commits should end up _inside_ the branch. but if you break _after_ the branch-end, the commits shouldn't.
-
could be hard, esp. since we'd still drop you off at that branch, since cannot drop you in another branch since there's no commit there
-
{{[[TODO]]}} ~~unless we add an empty commit so that you can add~~
-
ah wait nvm, you'd still end up in the end of the branch (i.e. you'd be adding commits to the end of the branch).
-
{{[[TODO]]}} to solve this, instead we'd create a temporary branch at the targeted location (oh but we'd still need the empty commit, and the branch would point to it), and then check you out into it, and then clean up when applying
-
the whole point of why this is needed is that we do not want to add commits into the previous branch. but you cannot add commits to the beginning of the newer branch either, only it's end, so we create a branch in between the 2 so that you can naturally go at it.
-
-
-
-
-
-
-
(hidden) Y7bKiytf2
-
(hidden) lkDvVSh5w
-
(hidden) AuYRlEIFx