that, again, depends on your workflow. For one project, I
interactive-rebase my feature branches often, and merge them into master
when they are finished; after that, they can live forever in the repo, and
if the feature needs a fix or change, I can check them out. For another
project, I squash-commit the feature branch then delete it. In a third one
I squash and don't delete. You decide :)
On Jul 20, 2016 05:55, "Michael" <keybou...@gmail.com> wrote:
> Lets say I've got a topic branch. I've made a bunch of commits. It's
> messy. But it's done.
> As I understand it, best practice is to do a squash commit of the whole
> thing onto the parent branch (develop or master, depending on workflow).
> And I can do that.
> What do I do with the leftover? I thought I could tag it as "closed", but
> I can't use the same tag more than once. What's the best way to mark it as
> done, or should I just delete the branch label and let it be garbage
> Entertaining minecraft videos
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.