-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Transfer of the repo to scala/scala3 #19848
Comments
lampepfl/dotty
to scala/scala3
lampepfl/dotty
to scala/scala3
This will break the universe, but better late than never 🥲 |
During that operation, the CI will not be operational. Any in-progress job will be canceled as we start the transfer. Please do not attempt to restart jobs. Avoid submitting PRs or pushing to branches with open PRs during the operation. Once the repo has been transferred and the CI is back online, existing PRs will need to be rebased on the latest GitHub will automatically redirect HTTPS and git requests, so no immediate action will be required from your side for your links to keep working. We will post a new message here when we start and finish. Sorry for the disturbance, and thank you for your understanding. |
lampepfl/dotty
to scala/scala3
lampepfl/dotty
to scala/scala3
on Wednesday March 6, morning CET
lampepfl/dotty
to scala/scala3
on Wednesday March 6, morning CET
I may be taking a joking/casual remark too seriously, but: what are you concerned might break? (besides Dotty's own CI, which will be taken care of during the upgrade) GitHub is really good at redirecting existing links when a repo moves. |
It was mostly a joke.
Any automation that is taken for granted that it works. Maybe some scripts won't take the redirection kindly, who knows... I won't be surprised if we end up being surprised ;) I think this change is important for Scala, so it will be worth it nonetheless, even if there are problems. |
Hi everyone, |
It’s done! You can now all resume submitting PRs and pushing to branches. We recommend that you rebase existing PRs on top of the latest main if you push something new. |
All in the title.
The text was updated successfully, but these errors were encountered: