Open jackfirth opened 2 months ago
Sure, I'd be open to that, although I'm also happy with the status quo and don't mind too much if there are multiple solutions to the same problem. Do you know if transferring the repo directly would break existing users? Or would we have to do something along the lines of
(or some variation of these steps) ?
I see this interesting snippet in the GitHub docs:
If the transferred repository contains an action listed on GitHub Marketplace, or had more than 100 clones or more than 100 uses of GitHub Actions in the week prior to the transfer, GitHub permanently retires the owner name and repository name combination (
OWNER/REPOSITORY-NAME
) when you transfer the repository. If you try to create a repository using a retired owner name and repository name combination, you will see the error: "The repositoryREPOSITORY_NAME
has been retired and cannot be reused."
Visiting the original repository in the browser redirects to the new one. I have a feeling they do the same thing for references to the old action, and that's why you're not allowed to reuse the old name. The docs don't mention what happens to actions specifically though.
So it sounds like everything should Just Work, IIUC, although the retiring does make me a little anxious that we won't be able to transfer it back if necessary for whatever reason (but I don't expect that to be necessary). I'm open to doing it, but I'm curious what others think as well. I won't have time to do it until at least next week, anyway.
I think the community has pretty much standardized on your action as the default approach to using Racket in GitHub Actions (RIP jackfirth/racket-package-ci-action my beloved). Would you be interested in transferring it to the Racket GitHub organization? That way people might be more likely to try improving this action instead of making their own and duplicating effort.