-
(hidden) EGXciMxb0 [[(hidden) H8VAVbNIn]]
-
(hidden) vUNm7tXEf
-
(hidden) Dh3xFJ12_
-
(hidden) 2hmPCbeVS
-
(hidden) c7geYh48J [[(hidden) 7CRWJsCnJ]]
-
(hidden) gFv64PtZG
-
(hidden) UjMJMBRRs
-
[[git-stacked-rebase]]
-
found out there's ofc more people doing stuff like this!
-
from [[(hidden) tv1zOVzED]]
-
{{[[TODO]]}} #read https://news.ycombinator.com/item?id=29255195
-
{{[[TODO]]}} #read https://gerrit.googlesource.com/gerrit/+/refs/heads/master/lib/
-
{{[[DONE]]}} #read https://graphite.dev/blog/post/DThX8ffP1gmxWJChEv0y
-
https://jg.gg/2018/09/29/stacked-diffs-versus-pull-requests/
-
(hidden) tmDDEqjaw #[[(hidden) 7c2C8PgIV]]
-
(hidden) hNj6arDcd [[(hidden) 37rJr30_V]] [[high signal]]
-
(hidden) 0DLpAOh8w
-
(hidden) 3WXjpPBsx [[(hidden) BnNcnokoC]] #[[(hidden) lh-ZUdNjE]]
-
(hidden) FgxWyg1Xm #[[(hidden) DY6wPnICE]] #[[(hidden) unlH_9R0B]] [[(hidden) JkF9j8PEK]] [[(hidden) 7_b216tQu]]
-
(hidden) 3UhYBfam0 [[(hidden) WgQQoInBs]] [[(hidden) 9-UljKXNz]]
-
(hidden) D_Wvo7lU1
-
(hidden) oH8URqn1D
-
(hidden) 4xvYZ-rgt [[(hidden) sJRzxsUIN]]
-
(hidden) OLp_8EcCt
-
(hidden) sImn6BH-b
-
(hidden) ndrWjN5T4
-
(hidden) 6q69TUWWW
-
{{[[TODO]]}} (hidden) 4Ryf6ATW9 #read
-
{{[[TODO]]}} (hidden) AoMI9ODmZ #read
-
(hidden) yc9QvtC6L
-
-
(hidden) 20kF6hOHf #[[(hidden) NZ49MYFWb]] #[[(hidden) 4mVW5p7mL]]
-
(hidden) qK49fguzB [[mixed signals]] #[[(hidden) JEA40P17v]]
-
(hidden) jkpsBkjJT
-
-
(hidden) bqkWX_59i
-
-
(hidden) LiSXhVosV
-
-
-
(hidden) FAG-HVI9X #[[(hidden) 7c2C8PgIV]]
-
https://docs.graphite.dev/
-
-
-
-
-
{{[[TODO]]}} `--sync` will be very interesting. we'll have to tackle both local & remote changes (local at first, remote later, if ever possible)
-
something like 3-way (or 4-way? maybe not, if successfully `--apply`ied) merge
-
no clue how to do properly tbh, will just need to experiment a lot
-
{{[[TODO]]}} would also enable us to explore the workflow of jumping between branches & editing there directly, instead of currently doing everything mid-rebase (either moving commits in git-rebase-todo file, and/or marking commits with `edit` / just `break`ing)
-
-
{{[[TODO]]}} if user doesn't provide the `initialBranch`, could launch `fzf` to allow them to search for the `initialBranch` (or `initialCommittish`, when implemented)
-
{{[[TODO]]}} for extracting a branch from the stack, could simply allow dragging the commits & the branch-end to the very beginning of the stack, i.e. before the "branch-end-initial"
-
{{[[TODO]]}} something [related](((4-ipzrx1j))) for created a new branch-end __after__ the branch-end-last.
-
{{[[TODO]]}} could have "sugar" options (i think mentioned this before, for the `reword` functionality)
-
{{[[TODO]]}} allow to swap the order of commits (& branches) in the `git-rebase-todo` file
-
would be useful. i'm often confused
-
but, gotta be careful w/ not giving people the wrong habits, because you could easily forget this / get confused when doing a regular rebase
-
maybe would incentivize users to use `git-stacked-rebase` as the default, i.e. to replace the regular git-rebase with it? 👀
-
{{[[TODO]]}} could be achievable, if we provide a way to directly pass in git rebase's commands to the underlying git rebase!
-
doable. already had an idea for `--` to forward args to the regular rebase
-
but would be best if this isn't needed.
-
{{[[TODO]]}} we could have a list of git rebase's supported args, so that we pass them in automatically
-
{{[[TODO]]}} and only if there's a new command in git rebase, only then we'd error out, and
-
re: ((sjdQWUl_U))
-
-
-
-
-
-
-
[[additional research]]
-
-
{{[[TODO]]}} when we mature, at least in [[level 1 of gsr]], advertise at https://stackoverflow.com/questions/61216739/how-to-rebase-with-multiple-stacked-branches-in-git
-
{{[[TODO]]}} fix issues w/ different node versions
-
-
(hidden) EeWzKDm5M
-
(hidden) 5I84pwSDk
-
(hidden) hCOZwL4J9
-
(hidden) JFLT2_iYn
-
(hidden) VTGxUTGfF
-
(hidden) 7DnXC2n3Z
-
(hidden) 0v7B1VzLI