On 2016-07-20, 06:02 GMT, Charles Manning wrote:
For example let's say you are using some fault tracking database (eg. trac). It often makes sense to do the fix on a topic branch (eg. fix-trac-1234). If you leave the branch in place after merging it you can then refer to the branch in the trac notes and see what fixes were used to fix the bug (and reopen the bug if it needs another kick).

Well, IMHO, the ticket should lead to the commit(s) on master actually fixing the issue, not to the topic branch which has in the end nothing to do with the shipped product.

And to the original question. Of course, it all depends on the workflow, but I think the right question to ask is what you expect to do with those leftovers hanging around? Merge them eventually (make a topic branch rebased on master until it is merged), discard (just do so), or leave them around as notes for latter development (just left them hanging in the repo; branches and commits are cheap in git)?


https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8

If Patrick Henry thought that taxation without representation was
bad, he should see how bad it is with representation.

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.

Attachment: pgpaF8z_XGb_9.pgp
Description: PGP signature

Reply via email to