Skip to content
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

Add about renaming existing packages #7547

Merged
merged 4 commits into from
Jan 6, 2020

Conversation

oxinabox
Copy link
Contributor

@oxinabox oxinabox commented Jan 5, 2020

From discussion with @ChrisRackauckas and others on Slack

Fixes #7555

Copy link
Contributor

@nickrobinson251 nickrobinson251 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for adding this 👍

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Co-Authored-By: Nick Robinson <npr251@gmail.com>
Copy link
Member

@ericphanson ericphanson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very helpful!

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@oxinabox oxinabox changed the title Add about renaming existing Add about renaming existing packages Jan 5, 2020
@DilumAluthge
Copy link
Member

It seems like there is a consensus in favor of this PR.

If nobody objects, I’ll merge this PR tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

What are the steps to migrate a registered package to an organization?
5 participants