News for hackers. Stuff that matters.
Re:Git Koans (2013) by an_account on Thursday January 12, 2017 @12:20AM (#13379991)
As long as the branch hasn't been deleted, it's possible to figure out based on the commits, correct? (Not exactly easy, but possible.)

And if the branch has been deleted, which typically happens after merging, then there's not much reason to know the branch name.

Is there something I'm missing here?

Re:Git Koans (2013) by KayEss on Thursday January 12, 2017 @01:18AM (#13380176)
> then there's not much reason to know the branch name

Most likely the branch names give you a good deal of information in working out why things have happened.

Re:Git Koans (2013) by qznc on Thursday January 12, 2017 @05:02AM (#13381126)
That information should be in the merge commit message. If you merge something git will offer you a default commit message like "Merge branch 'foo'".

(assuming a non-fast-forward commit, where the branch is not really a branch because nothing happens in parallel)

Re:Git Koans (2013) by lmm on Thursday January 12, 2017 @05:28AM (#13381212)
So can I ask git to show me the merge commit that relates to the commit I'm looking at?
Re:Git Koans (2013) by mooneater on Thursday January 12, 2017 @02:17AM (#13380418)
This
Re:Git Koans (2013) by Vinkekatten on Thursday January 12, 2017 @08:22AM (#13381956)
We use Jira and bitbucket - most if not all branch names contain an issue number and the name of the issue, while commit messages can be more cryptic. This is often helpful when the branch has been deleted, as it usually is.