-
Notifications
You must be signed in to change notification settings - Fork 88
rename to scala-library-compat #327
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
Conversation
Travis-CI didn't pick up on the repo name change at first, but I think I coaxed it into switching over |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we tell scala-steward about the name change? Should we open a PR somewhere else?
I think it would be okay to just let that slide, actually. If people are doing okay using the old version, it's not critical to get them to move, IMO. (But let's @-mention @scala-steward and see if the crew over there has anything to say...) But when we release under the new name and the wider scope, I do think we should tweet about it from scala_lang. I added a reminder on that to #328 |
Scala Steward can change organizations but it can't change artifacts (yet). I'll update the name of this repo in https://github.com/scala-steward-org/repos/blob/master/repos-github.md so that you'll continue receiving PRs from @scala-steward. |
That’s very nice @fthomas, thank you! |
reverting in #356 |
fixes #317
note that I already renamed the GitHub repo
#328 has the associated README.md changes separately, to be
merged once we've actually published under the new name
this PR disables MiMa, but I left a breadcrumb in #328 to remember to re-enable it later