-
(hidden) 6PpBTr0-t #read
-
(hidden) IjXpYThjh
-
(hidden) hBJSY0fOI
-
(hidden) yKNWpLDTG
-
(hidden) ifCJTtnDk #[[(hidden) S-ygYfi0j]]
-
{{[[TODO]]}} (hidden) YctcnfVlP [[(hidden) V8WtQHk_B]]
-
(hidden) LFyHH0leO
-
[[codemods]]
-
{{[[TODO]]}} css stuff
-
{{[[TODO]]}} talk to upstream re: supporting different runners ([[(hidden) DTTuZxhoc]] / [[(hidden) HwSsfeahD]] etc.), or at least specifying before/after commands
-
{{[[DONE]]}} allow comment when needing a manual value in `add-missing-jsx-attribute`
-
{{[[TODO]]}} updating info
-
{{[[TODO]]}} quick info for what to do next (linter etc)
-
-
(hidden) DvrQw6XbS
-
-
(hidden) vd4soRWyT
-
[[git-stacked-rebase]]
-
{{[[TODO]]}} can take inspiration from e.g. [[(hidden) TVhpQMM3V]]:
-
on the [[(hidden) hLbnDaAwS]] stuff - lol, i think we've come full circle now - i now realize that in our ([[js]]) environment, using `throw` + `catch` for errors, and `return` + `.then`/`await` for success, is all that's needed!
-
{{[[TODO]]}} the initialBranch travelling together and eventually ending up the same as latestBranch
-
oh boy, something's def. wrong
-
{{[[TODO]]}} i think we need to switch to using [[git]]'s native `rebase`
-
{{[[TODO]]}} would prolly fix this
-
{{[[TODO]]}} won't need to create the initial `git-rebase-todo`, only parse it (already doing it)
-
{{[[TODO]]}} can allow users provide further args to native rebase after `--`
-
{{[[TODO]]}} only problem is that it at least __seems__ hacky -- users could have their own scripts set up, and invoking these would be far from ideal
-
-
-
-
(hidden) 7jZzvAn9l
-
(hidden) XLSsxgT1t
-
(hidden) 57OS6vFJ1
-
(hidden) FW_05ytKD