Change Details

GitHub just [[ https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git | announced ]] they will remove support for the git:// protocol Unfortunately, we [[ https://forge.softwareheritage.org/source/swh-loader-git/browse/master/swh/loader/git/loader.py;e7476caee896c047e716971fce779168f4a2be6c$172-173 | depend on it ]] to clone efficiently. So we need to either: * Ask GitHub to keep supporting it (at least for us) * Figure out an alternative

GitHub just [[ https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git | announced ]] they will remove support for the git:// protocol in mid-march (with a brownout in mid-january) Unfortunately, we [[ https://forge.softwareheritage.org/source/swh-loader-git/browse/master/swh/loader/git/loader.py;e7476caee896c047e716971fce779168f4a2be6c$172-173 | depend on it ]] to clone efficiently. So we need to either: * Ask GitHub to keep supporting it (at least for us) * Figure out an alternative

GitHub just [[ https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git | announced ]] they will remove support for the git:// protocol in mid-march (with a brownout in mid-january) Unfortunately, we [[ https://forge.softwareheritage.org/source/swh-loader-git/browse/master/swh/loader/git/loader.py;e7476caee896c047e716971fce779168f4a2be6c$172-173 | depend on it ]] to clone efficiently. So we need to either: * Ask GitHub to keep supporting it (at least for us) * Figure out an alternative