Skip to content

Prevent Git clients to interact with Mercurial projects

In this MR, the first commit is a minimal hack that prevents this by introducing a blank refusal in the internal API call that's used to grant access over SSH. But it's not really future proof, relying on the fact that we don't have any legit Git call over the web.

In the second commit, we introduce an ad-hoc protocol, depending on py-heptapod!14 (closed), which is more future proof, but also more risky at this stage (it passes all the MR functional tests for me though).

Merge request reports