- There are ranges in the "git" block, but it doesn't mean they're doing anything with it (until it's in the DNS or they publish specific IPs are safe to connect to it doesn't mean anything)
This page is actually in the wayback machine (thank you!!!) and the same ranges were already listed in 2022 (not in 2021, didn't look for exact first occurence)
http://web.archive.org/web/20220710073458/https://api.github...
- Great. I have a few IPv6-only hosts, and having to workaround GitHub being ipv4-only was a pain, especially during turnup, since my host config is stored on GitHub.
- I guess this helps the nomad crowd more than us cubicle jockeys right? Also iot? You guys can build ci/CD straight to iot edges.
- Bit of both, if you're building from a service provider you now don't need v4 to push (OVH, Hetzner, etc.)
Less so than road warriors, who are typically CGNAT'd anyway.
- Long overdue transition. Native IPv6 support for Git SSH remotes solves significant NAT bottleneck issues for automated CI/CD pipelines at scale.
- It must be a snow day in hell.
- see the "git" block for remote IPv6 ranges. This indicates they may be moving forward on ipv6 .
"2a0a:a440::/29", "2606:50c0::/32",
- What does this mean?
- It means if your network is IPv6 native, you don't have to waste a very expensive IPv4 IP address, or proxy through one, to connect to it
- Well FINALLY!
