docs: link distribution page to roleweave per-deployment login issue - #81
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
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.
What
docs/DISTRIBUTION.md: the open item for roleweave per-deployment client login now linksthe filed issue (feat(auth): per-deployment login for the client — sessions scoped to each deployment, git-credentials style roleweave#395), completing the cross-reference promised by the
authentication consistency principle section.
Why
The distribution page and the client requirement must point at each other so implementers
land on both the strategy and the tracked work item.
Validation
Docs-only link change; no runtime behavior change. Prettier clean. No CHANGELOG entry:
the page itself was already announced in the previous Added entry.