What would people think about if I moved chruby, ruby-install, ruby-versions, and maybe rubygems-tasks, into a new GitHub Org? GitHub does support automatic redirects for moved repos. It would give it an air of official-ness, instead of going to my GitHub. I would probably have to do this in ruby-install 0.10.0 and change the URL for the ruby-versions repo, which it downloads version info from.

Only downside is it would automatically close *ALL* outstanding PRs.
#rubyinstall #chruby

I also need to update the signing mechanism. Either I need to generate a new PGP 4096 bit key and load it onto a YubiKey, or switch to sigstore (which uses OpenID) which is what all of the cool kids are apparently using.
https://www.sigstore.dev/
#rubyinstall #chruby
sigstore

![sigstore logo][logo]

sigstore
I would probably want to create a *new* ruby-versions repo in the new org, and `git push --mirror` to that one as well, and still keep https://github.com/postmodern/ruby-versions repo in place for older versions of ruby-install to allow users to slowly upgrade to the new ruby-install and ruby-versions repo. I am not 100% certain that https://raw.githubusercontent.com/ supports redirects for migrated repos.
GitHub - postmodern/ruby-versions: A common repository of ruby version metadata

A common repository of ruby version metadata. Contribute to postmodern/ruby-versions development by creating an account on GitHub.

GitHub
Confirmed that https://raw.githubusercontent.com does transparently re-route requests to the new repo if a repo is migrated to a new org/user. This simplifies such a migration.
GitHub: Let’s build from here

GitHub is where over 100 million developers shape the future of software, together. Contribute to the open source community, manage your Git repositories, review code like a pro, track bugs and fea...

GitHub
@postmodern If you’re doing a move, I’d also encourage you to consider a platform not owned my Microsoft. Codeberg , Forgejo, or GitLab maybe?
@edward GitHub supports migrating repos to other users/orgs and sets up redirects so everything just works. Doing a hard move off of GitHub would mean I would have to maintain two copies of ruby-versions, until people slowly upgrade to ruby-install 0.10.0. Plus, there's no easy way to export issues from GitHub and import them into another platform.
@postmodern Yup, certainly a lot more work. Not without it's advantages, but I’m not the one who has to do it 😅 Thanks for considering.
@postmodern @edward do you reference issues or pulls by number in commit messages? Existing commits might link to the wrong place, the old repository pull / issue. The loss of issues / pulls is annoying.
@postmodern Does transferring a GitHub repository close all outstanding PRs? I've done transfers multiple times, but I'm not sure if I've seen it.
@k0kubun yes, and they warn you about that.
@postmodern I see. The repositories I transferred were maybe the ones that tend to have no open PRs (while they do have open issues), so maybe that's why. It sounds annoying.
@postmodern I mean... I recognize your handle of old, but if that feels like a thing you want to do, I say go for it. Those PRs had it coming anyway. 😜