Git branch deletion

In Git, what does “deletion” of a branch mean?

Will it be gone from the repository? Or will it still be navigable to via git branch?

  • Git rebase continually fails and requires manual merge intervention
  • How to find the current git branch in detached HEAD state
  • Centralized GIT workflow/deployment - Repository Initialization and Feature Branches
  • branch metrics link on Android app
  • Display all first-level descendant branches using Git
  • Listing and deleting Git commits that are under no branch (dangling?)
  • What I really want to do is mark a branch as “dead end”, i.e., the branch is so far from master, that nobody should use it as a starting point, though there were some good ideas down that branch, so we’d like to keep it, for reference.

  • Git merge strategies: spaces make default shows no conflict and bring unexpected results
  • How to resolve Git error: “fatal: BUG: get_tempfile_fd() called for inactive object”
  • How does git rerere figure out the similarities between two conflicts?
  • How can I reset my working copy to a specific commit?
  • How does git push handle a backlog
  • Can I get git not to merge files, but simply copy newever ones
  • 4 Solutions collect form web for “Git branch deletion”

    You can delete the branch, but tag it first, so that it’s history doesn’t disappear. This way, the branch doesn’t show up in the branch list, which should hopefully deter people from working on it, but the work won’t be permanently erased (even after garbage collection is run). For instance, whenever I have a branch that has become irrelevant, but I’m not prepared to permanently delete it, I tag it as “archive/<branch-name>”.

    While on master or some other branch:

    git tag archive/foo foo
    git branch -D foo

    This creates a tag named archive/foo from the foo branch before deleting foo. You can also add a message to the tag, that explains what is in the branch, why it existed, why it’s now a dead end, etc.

    git tag -m 'Foo is deprecated in favor of bar' archive/foo foo

    The ability to record why a branch is being deprecated is perhaps an advantage of tagging versus moving branches to an alternate namespace.

    If you ever need to resurrect a branch that has been archived this way, it’s as simple as:

    git branch foo archive/foo
    git tag -d archive/foo       # Optional

    Now the branch is back as though it was never deleted.

    Git branches are stored as references to a revision. If you delete the branch, the reference is removed; if nothing else references that revision, it will eventually be garbage collected. Also, if you delete the branch then it’s properly gone (from your repository). If you want to mark a branch as deprecated but keep it around for later use, you could move the branch to a subdirectory:

    $ git branch
    * master
    $ git branch -m testing_feature_one deprecated/testing_feature_one
    $ git branch
    * master

    Alternatively, you could create a separate repository for deprecated branches, pull them across then delete them from the original. In either case, you’re going to affect any users who are following the branches — the content of their repository won’t change (and neither will any of their branch names), but if they try to pull again, they’ll have to change their target in their configuration.

    git branch -D <branchName> will delete your branch from repository. You will not be able to see it or navigate anymore. Also you will lose all file changes made in that branch.

    It won’t be navigable via git branch and until garbage collection is performed, it won’t be lost from the repository.

    If you want to mark the branch in question as a dead end then simply do so (git may not do this for you but you certainly can)!

    Labelling it (in any way you prefer) as a historical reference works.

    Git Baby is a git and github fan, let's start git clone.