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

Rename ewels/MegaQC -> MultiQC/MegaQC #485

Merged
merged 3 commits into from
Dec 19, 2023
Merged

Rename ewels/MegaQC -> MultiQC/MegaQC #485

merged 3 commits into from
Dec 19, 2023

Conversation

ewels
Copy link
Member

@ewels ewels commented Dec 18, 2023

I'm in the process of moving MultiQC and related repos off my personal GitHub account and over to the MultiQC GitHub organisation.

I'd like to move MegaQC too, is everyone ok with me moving it to MultiQC org?

Only downside I can see is that the name becomes MultiQC/MegaQC which is maybe a bit of a typo-prone mess. But hopefully it's clear enough.

I'm also taking this as an opportunity to rename default branches from master to main.

@ewels
Copy link
Member Author

ewels commented Dec 18, 2023

I'll leave this here until tomorrow so that folks get a chance to see and comment, but barring any concerns I'll aim to merge and rename around this time tomorrow 😃

@multimeric
Copy link
Collaborator

Looks fine to me, we'll see if anything breaks after the actual change of ownership. The CI failures are probably irrelevant here.

@ewels ewels merged commit d1c2ea3 into master Dec 19, 2023
6 of 20 checks passed
@ewels ewels deleted the rename-ewels-multiqc branch December 19, 2023 12:06
@ewels
Copy link
Member Author

ewels commented Dec 19, 2023

Done! I also made a new DockerHub repository multiqc/megaqc and pushed the :latest and :v0.2.0 tags.

Shout if anything needs fixing!

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

Successfully merging this pull request may close these issues.

2 participants