-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
per-worktree machete option #517
Comments
Haha I didn't know this xkcd... applies here perfectly indeed 😅 could you provide more details on how your workflows around worktrees look like? even pieces of bash_history could be useful (unless confidential ofc) |
i have a script that deletes a worktree, and removes local branches that have been merged to the remote and aren't found in any other worktrees. its also handy for keeping track of which local branches are 'tied' to which worktrees. i know they aren't actually tied but with long builds you generally want to keep a worktree on the same version for as long as possible. |
Okay! so |
thats awesome, thanks :) |
Whoops (coz I'm a Fedora and not Mac OS/Homebrew user myself, I'm only publishing this package to Homebrew tap)... what does actually backdating correspond in Homebrew? Is it equivalent to simply downloading newer versions for the already installed software (like |
im not entirely sure.. its slow and bloated, but its the package manager that we have... |
they used to support backdating to any old version, but now they have to be specifically created as separate releases i guess |
Oh! okay, that's good, no problem then with shipping that feature in v3.10 or v3.11. I suppose you mentioned
for the sake of installing a previous version which has the old logic for worktree's .git/machete location, i.e. v3.6.0 or earlier, right? If so, I'd probably un-install git-machete from Homebrew, and use |
ahh yeah ill try it with pip. thanks :) |
To be released soon in v3.11.0 |
https://xkcd.com/1172/
i actually found this very helpful, would be great if there was an option for it.
The text was updated successfully, but these errors were encountered: