Somehow this is not my experience at the moment. I'm not sure if that would be more efficient than later running multiple instantiations of git filter-branch -subdirectory-filter on copies of the git repo but, in any case, I would still like to break the link with the origin. git fetch origin -prune doesn't delete local branches Ask Question Asked 7 years, 1 month ago Modified 7 months ago Viewed 69k times 93 At one point I thought that git fetch origin -prune deleted local branches that were no longer present on the server. I realise that I could use the -T flag to git-svn to clone the relevant subtree of the subversion repo in the first place. As you can see, we now have the following: One branch that is connected to an existing remote branch ( branch1) One branch that had an existing remote branch, but the remote branch is now gone ( branch2) One local-only branch that never had a remote branch ( branch3) This should cover all the cases in a 'normal' environment. I can prune the repo to just the wanted subtree using: git filter-branch -subdirectory-filter path/to/subtree HEADīut the resulting repo still contains all the revisions of the now-discarded subtrees under the origin/master branch.
#Git delete branch in origin full
Each of the new git repos should have the full history of just the relevant branch. To delete a remote branch, you will simply right-click on the target branch from the central commit graph or the left panel and then select Delete
Longer question: I want to take an existing subversion repo and make a number of smaller git repos from it.
Basic question: How do I disassociate a git repo from the origin from which it was cloned?Īnd I want to remove all knowledge of origin, and the associated revisions.
0 kommentar(er)
