Advertisement
Advertisement
β‘ Community Insights
Discussion Sentiment
50% Positive
Analyzed from 133 words in the discussion.
Trending Topics
#worktrees#branches#author#using#magit#old#due#agents#love#didn
Discussion Sentiment
Analyzed from 133 words in the discussion.
Trending Topics
Discussion (4 Comments)Read Original on HackerNews
I've solved this by running thin bash script wrappers that keep the workflow SVN-like with a root directory that contains per-branch directories and a hidden bare repo).
My branches end up in a tree structure (no shit!), and I rebase and merge up stream as changes land. I guess it could be more automated, but the only tedious part is remembering to remove old worktrees and prune the old branches