chore: update StacklokLabs references to stacklok#108
Merged
Conversation
Ahead of transferring this repo to the stacklok org. Points the mcp-builder clone/PR/issue links at stacklok, and updates the mcp-template-py links which already moved to stacklok/mcp-template-py. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lorr1
force-pushed
the
chore/rename-stackloklabs-to-stacklok
branch
from
24b4bec to
7f3c90a
Compare
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
1 participant
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.
Updates all in-repo
StacklokLabsreferences tostacklokahead of transferring this repo to thestacklokorg.README.md— clone URL for mcp-builder, plus threemcp-template-pylinks that were already stale (the template moved tostacklok/mcp-template-py).docs/rfc-custom-mcp-server-builder.md— PR Align mcp-scope auth schema with OAuth2/OIDC reality #99 / issue Align mcp-scope.yaml auth schema with OAuth2/OIDC reality #94 links.Verified no
StacklokLabs/stackloklabsreferences remain in any tracked file. A full-history secret scan (gitleaks, all refs) came back clean, so the repo is safe to make public after transfer.🤖 Generated with Claude Code