-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is this not under OpenAstronomy? #3
Comments
I created it in a hurry and never got around to moving it to OpenAstronomy, and there are too many users to move now. We could fork it to OA if you'd prefer to have it there? |
I think you can still move it and it would still work as long as you keep your fork updated. |
Also https://github.com/astrofrog/batchpr is very handy for doing auto updates to all your users. |
fwiw, if you move a repo to a different org, the original location will redirect, as long as you don't fork it into the same name again. We migrated |
The note on this documentation page seems to suggest that it won't redirect? In any case, I am keen to move this to OA as that was my initial intention. I'll then quickly fork it back to here. |
Now sure how the docs page you reference here is relevant. xref for an action that we moved from a personal account into an org without experiencing any issues: scientific-python/circleci-artifacts-redirector-action#50 (comment) and the PR |
Nice! Looks like it'll work without the fork. I got the doc link from actions/runner#1695 but just seeing the last comment now pointing out the confusion |
I see that this is used here: https://github.com/OpenAstronomy/github-actions-workflows/blob/7e9fc90251e98f81f83e01539f1aa143c26643d1/.github/workflows/publish.yml#L223C15-L223C44
The text was updated successfully, but these errors were encountered: