Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've only recently tried my hand at forking in github and would like some "best practice" advice.

I created a branch in my fork, and that branch got pulled into master of the upstream project. It no longer appears in the network graph, but it's still there on the github. Is it safe for me to delete this branch on the fork now?

Edit: Just to clarify, I'm checking if this conflicts with github's "don't change history" rule.

share|improve this question
Also see the question in… – PhoneixS Aug 12 '14 at 9:27

When you add something to master branch, it's there for good. Merging another branch to master is just adding things from other branch to master.

When you delete that other branch, the history inside the branch is lost if you rebased it. But it does not make much sense anyway, once the changes are in the master branch.

So, you can safely delete your branch if you don't want to continue development within it.

share|improve this answer

If you're worried about upstream's code magically disappearing if you delete your branch, don't. Once they pull it, it's there (more or less) for good.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.