git-refactor

words:	1 + 234 = 235
last update:

#public

Linked Mentions (3 in 3 pages)

January 26th, 2022 (1)
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] -- [[git-refactor]] -- take uncommited changes, do the equivalent of seeing the git blame of the code that was there before modifying, create fixup commits and apply them via [[git-rebase]]
  - wanted this for a while, but now becoming more clearer, esp. since [[git-stacked-rebase]] is getting more mature
March 21st, 2022 (1)
- {{[[TODO]]}} [[git-refactor]] "cleanup reduce-path.js - consistency w/o semicolons"
June 14th, 2022 (1)
- {{[[TODO]]}} about [[git-refactor]] - if we could understand the dependency graph, then there's a lot of cool stuff we could do
  - {{[[TODO]]}} e.g. displaying a hierarchical / graph view of how the changes in a PR depend on each other, split by files and/or functions
    - could even integrate thru multiple PRs if we're doing this sort of thing
      - #observation it's all the same thing, just grouping the previous one into a bigger one. like a tree, or layers.
        
        and there's probably edge cases for either leaf nodes, or the root, or both
        
        e.g. in [[roam]], only the root is the exception (the Page), everything else is a Block.
        
        though, if we'll have multi-graph mode in the future, then that's a new world. probably similar to stacked diffs / pull requests :D
        
        #observation the 3 projects -- [[codemods]], [[roam-traverse-graph]] and [[git-stacked-rebase]] -- were all started at a similar time & i often saw one have similarities to another. feeling this again. [[(hidden) K0RqswvNf]] [[high signal]]
  - {{[[TODO]]}} could also potentially reuse this solution to improve [[codemods]] -- the [[(hidden) 9ipeOcvbC]]