Repository navigation
Standardize ContextMesh branding after repository rename - #37
Merged
Merged
Conversation
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
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.
Scope
Branding/metadata cleanup only after renaming the repository to
Deep-Sixed/ContextMesh.Changes
ContextMeshin the README and release notes;Deep-Sixed/ContextMesh/cd ContextMesh;pyproject.tomlHomepage, Repository, and Issues URLs to the renamed repository;The existing
v0.1.0GitHub Release has also been updated in place toContextMesh v0.1.0with the synchronized release-note text. The release tag and target commit were not moved.Temporary helper workflows used to perform the repository/release text synchronization were removed before opening this PR; the final diff contains only
README.md,RELEASE_NOTES.md, andpyproject.toml.No code, package name, import namespace, CLI command, tag, or version changes.