Conversation
Collaborator
|
Think the CI might be currently failing because it's looking for links with the old repo name, guessing this PR will fix it? |
Aurashk
approved these changes
Oct 9, 2025
Member
Author
|
@Aurashk Yep, sorry about that! I thought GitHub automatically set up redirects, but I guess that's only for the main repo and not the docs. I'll merge this now so you can update your PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR changes the name "MUSE 2.0" to "MUSE2" everywhere (in the docs, code etc.). I've already renamed the repo, so the new URLs should work fine. The problem is that the name is going to become confusing the moment we release v2.1.0 (hopefully that won't take as long as the v2.0.0 release 🙃), so let's make it less ambiguous.
@ahawkes has signed off on this change.
Closes #895.