Replies: 3 comments 1 reply
|
@ogulcancelik this is a simple change - if you are ok with this i am up for creating a PR from my forked repo |
0 replies
|
hey, 0.7.0 is out and it brings the new plugin system: https://herdr.dev/docs/plugins/ this looks like a good candidate for a plugin instead of a built-in herdr feature, so i'm going to close this discussion for now. if you build or find a plugin for this workflow, please share it here so others can use it too. |
0 replies
|
Built this as a plugin https://github.com/persiyanov/herdr-fresh-worktree @ogulcancelik thank you for herdr! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
Worktrees in TUI are based on whatever is in local HEAD, it not necessarily is the freshest. Instead it would be goo to have conductor behaviour where base is taken from origin/HEAD (we can check
origin/HEADand if it does not exist rungit remote set-head origin --autoand then check again. If all fails we fallback to local.proposed change
Behavior when base = "origin_head":
git remote set-head origin --autosilently (creates origin/HEAD if missing, requires network)origin/HEADas the base ref togit worktree add -b <branch> <path> origin/HEADBackward compatible — default remains head (current behavior). No existing config breaks.
why you want this
I want my worktrees fresh - I often work in many repos. Less conflicts later when merging.
I am willing to implemnent this
All reactions