Right, “parent branch” implies a tree structure, but git is a DAG. You might have a specific workflow such that you can actually answer your question, but it w

Right, “parent branch” implies a tree structure, but git is a DAG. You might have a specific workflow such that you can actually answer your question, but it won’t generally apply to all repos. Since a branch is really just a label for a specific commit, which may be at the end of a chain of successive parent commits, a branch isn’t really a first class structure, but a derived one. You can get the fork point of a branch, which is a common ancestor commit shared by another branch, but that fork point is a commit and may not have a branch label. That commit can have any number of other branches going off of it: how would you decide which one is the parent vs just another sibling? My assumption after looking at jj is that it is not as complicated as git yet. Give it time. It’s also not even as simple as git for many tasks, based on their own docs: https://jj-vcs.github.io/jj/latest/git-command-table/ https://jj-vcs.github.io/jj/latest/git-command-table/