Pulling git repository with mercurial evolve leads to duplicated tree of commits
We have a proof-of-concept working to push using mercurial to an heptapod instance (which for now has hg-git under the hood) and it mirrors to a git/github repo. One can push with mercurial, create a Pull Request, review it there, do an hg amend
, push with mercurial and the point discussed are resolved, and once the changeset is published the merge request on github is automatically closed. See some details on heptapod/heptapod#125 (closed) ... Nice. But...
(sorry if this is unsolvable, at least we'll know)
User A (who doesn't have hg-git localy) pushes mercurial (to heptapod) as :
graph BT
A --> B
A(init)
B(cs1 - published)
B --> C
C[cs2 - draft]
User B clicks on merge in the pull request on github
User C who has initial mercurial repo (from heptapod), pulls the git repo using hg-git and gets :
graph BT
A --> B
A(init)
B(cs1 - published)
B --> C
C[cs2 - draft]
B --> D
D[cs2 - draft]
If someone wants to work with this usecase, I can have a more detailed scenario so we can reproduce this.