Closed the-dijkstra closed 2 years ago
@jasonmccreary I'm on (#139167a)
Seems like it's expanding the *
that might be returned from the branch output...
@jasonmccreary I guess it is yes, because here is the output I get when running LANG=C git branch -vv | awk '/: gone]/{print $1}'
*
Yeah. Let me see if I can reproduce it locally and tweak that command to remove the current branch.
Seems like this would occur if the current branch were pruned. Which seems a bit odd.
Either way, I have added logic to exclude the current branch from the list of branches. Please check the code from main
and if it works, I'll tag 0.2.1
.
@jasonmccreary it works, but would it be normal ?, that the script now is taking some time to show output ? Compared to the other flags which show output immediately
Yes, if you have a lot of remotes or a slow internet connection as this command runs fetch
underneath.
I would expect subsequent runs to be faster though.
Actually, you are right. I forget that we are pruning, so it would be obvious that we do a fetch.
Description
Not sure what went wrong with the filter branch. But running
git trim -p --dry-run
is showing the following output:PS: I'm inside a Laravel project. Release before
0.2.0
was working just fine.