That is a more exotic question, but I am facing a problem when pushing to gitlab. It seems to behave differently (I explain below why) compared to bitbucket and github.
Is there any change to know the underlying git version they are using. Explanation (and please don't shout at me and tell me I should not do this, I know...... I would dare to do this in any reasonable sized repository) I admit I use mercurial and the so called hg-git plugin to deal with git repositories (the reason is simple I prefer a graph with so called named branches over one with git type of branches (or bookmarks for mercurial). Now I found a workaround for pushing, and a workaround for importing git branches into my mercurial named branches (it must be some kludge) because I have to use (hg) push -f That is a forced push, github and bitbucket accept that, while gitlab tells me abort: pushing refs/heads/main overwrites d30105a181c4 I will of course ask the hg-git developers But any comments especially concerning the git version would be appreciated. Regards Uwe Brauer -- Warning: Content may be disturbing to some audiences I strongly condemn Putin's war of aggression against the Ukraine. I support to deliver weapons to Ukraine's military. I support the ban of Russia from SWIFT. I support the EU membership of the Ukraine. https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/ -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/87tu24wggn.fsf%40mat.ucm.es.
smime.p7s
Description: S/MIME cryptographic signature
