-
{{[[DONE]]}} (hidden) PgqwSvH5b [[high signal]] [[(hidden) T_1jNRzLF]] #watch
-
(hidden) tFTvvR5Lj
-
(hidden) dI8Bu-bl1
-
(hidden) V1LGH-HW_
-
(hidden) xOw34K5N_ #[[(hidden) LQ_OH6SpP]] #[[(hidden) VgKGPjQIk]]
-
(hidden) y508gozuB
-
(hidden) jcYaDIovp
-
{{[[DONE]]}} (hidden) 4G1Sw7Zn8 #watch
-
(hidden) U3y3ZjSny
-
{{[[TODO]]}} (hidden) c9fQk2Qd_ [[(hidden) 5zJRT_DO-]] #read
-
(hidden) 4_yw9WDjZ
-
(hidden) 3H-AfTXBo
-
(hidden) vDlQUZEx1
-
(hidden) _wSPloHi4
-
[[roam-traverse-graph]]
-
(hidden) x04fH07iP
-
(hidden) ErL_0M6PT
-
[[git-stacked-rebase]]
-
{{[[TODO]]}} would be most interesting to see which changes you __can__ extract w/o merge conflicts; even better - how splitting a commit (multiple commits?) could help avoid the merge conflicts
-
{{[[TODO]]}} instead of `sugar.reverse` or whatever for reversing the commits, instead an alias for `git lg` (log --graph etc) that provides commits __in a reversed order__ would be better.
-
{{[[DONE]]}} for `--push --force`, i think i need to go thru branches in the reverse order
-
[[github]] just closed (emptily merged) one of the PRs because some commit was now already part of some other branch. pretty sure that pushing newest branches first, and oldest later, instead of the current "oldest first, then newest" would solve this
-
{{[[TODO]]}} need to somehow try this out (reproduce) 😅
-
-
{{[[TODO]]}} i think it'd be about time to always --apply (if possible)
-
the `--push` happening, when the `--apply` has not been done yet, because we didn't modify the local history (commits), but did modify some branches (e.g. order, or to which commit they point to) -- push will proceed without apply'ing.
-
in general, you'd expect the tool to work, so allowing yourself to be left in a half-broken state shouldn't be desirable.
-
-
-
(hidden) mSEQtNvkx
-
(hidden) QZtAq-Fau
-
(hidden) -C6sDCFfE
-
(hidden) HD3iHXQW5
-
(hidden) pOzrkxOXH
-
(hidden) rQ6DAe-77