• 5 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: August 11th, 2024

help-circle


  • Great question! I considered that, it’s what lead me to the idea to use DNS in the first place. The problem I had with that is that the ultimate URL path might change, not just the hostname. What happens if a repo has to move from github.com/org/repo to mycoolforge.net/repo?

    But there’s also another reason that I realized as I was working out the details of git-remote-helpers: What happens if your remote needs to change protocols? With doink you can swap from http(s) to ftp with an ip address instead of a hostname, or perhaps even some (future) git-over-whatever-p2p-network.

    So yeah if you’re swapping from a github-style forge to another github-style forge and you don’t need the flexibility, you definitely could just CNAME it! And that would probably be more robust, but it would also give you less future flexibility :P






  • Yeah, microsoft has owned github since 2018. I made this to help people and organizations move off of github, onto something like forgejo or sourcehut. But even after moving, all of those old issues, pull requests, comments, those need to live somewhere. A lot of people seem to use a script to recreate all their issues on their new code host, but that loses a lot of metadata and can only work if there’s a script for your new chosen host. Everyone else just archives the repo and leaves all that info there, which is great until people forget its there, or microsoft decides to start charging for issue hosting.

    So now, with GAH!, people can more easily move away from github, they don’t need to worry about what happens to their issues and PRs. It’s one less barrier to leaving github :)