In the increasingly large set of countries without absolute freedoms, such a thing is a given for any hosting provider.
No current country has absolute freedoms, except as a fantasy.
Edit: I didn't realise you were the person I responded to. I see what you mean, but I still think it's an important thing to discuss. It just won't be relevant to those people, which I can live with.
- if it's public, it's on github.
- if it's a private company project, it probably already has a home, on github or some other trusted commercial provider with cicd and all the trimmings.
- everything else goes here, as encrypted git bundles on s3.
i previously used git-remote-gcrypt for a long time. recently i've been thinking about how i wish worked with git, cicd, and infra. this is how i'm going to be working with that third bucket from now on.
the first bucket is fine, aside from lock of sha256 support.
the second bucket i'm still thinking about.
Anyone who needs to interact with the source code needs access to the plaintext version (employees, contractors, CodeClimate/CircleCI/Atlassian/Slack/etc type vendors, etc, all retain access), and people who don't need to interact with the source code should have their access removed in the first place.
This only protects you against a malicious/compromised hosting provider, but usually the hosting provider does more than just hosting, they have their own CI/CD features which need access to code. If you don't want the hosting provider to have access then you might be better off self-hosting Gitlab rather than dealing with restrictions like remotes can only have 1 branch.