Adam Bliss

Also "error code undefined" seems like a bug.

And if you close the submodule, it doesn't push at all.

Under the assumption that you only push one commit at a time, it would seem simple to examine the tip of the outgoing branch, and push to a synthetic meta...

I know it's not philosophically pure, but neither is the currently-implemented solution, and approximately 100% of real-world usage of git meta to date has been one commit at a time....

Agreed. But the tool is currently broken if you (a) have a different commit checked out than the one you're pushing or (b) have closed some changed submodules since git-adding...

sounds good to me!

Is there an issue in the libgit2 project we can link to?

Could you say a bit more about why you need the original local branchnames? Typically, in git, the local branch names are conidered ephemeral. They may persist in a commit...

Perhaps one could use the submodule..branch config in .gitmodules for this: https://git-scm.com/docs/gitmodules#Documentation/gitmodules.txt-submoduleltnamegtbranch I believe git-meta currently ignores this property (and we don't set it inside Two Sigma), but it might...

> We have a fairly standard release process. We create a permanent release > branch (across all repos of interest), and hotfix those release branches as > needed. > What...