docs: cover private HTTPS build repositories - #44
Merged
Conversation
Add the HTTPS quickstart next to the SSH block in the README: reuse of existing Git credentials at first install, the non-interactive csk config build-https command, and the CI environment variables. Rewrite the schema v7 transport paragraph in skill-authoring: both URL forms are accepted, a private repository requires explicit operator credential selection over either transport, and an HTTPS manifest URL must carry the .git suffix because fetch does not follow redirects. Add two troubleshooting entries: the three branches of build_repository_credential_policy_invalid with a command each, and the 301 no-suffix case findable by both the git error text and build_repository_source_unavailable, with the Windows credential-store note. State in the reference install matrix that compiled commands run only on macOS and Windows.
ivanopcode
force-pushed
the
docs-build-https
branch
from
August 24, 2026 20:09
dd90e08 to
858741f
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.
What
Documentation for the merged build_https broker (board story docs-build-https). The feature branch already shipped the external-build-repositories, cli.md, reference.md, and CHANGELOG sections; this PR adds the remaining four pieces.
README.md: HTTPS quickstart next to the SSH block (credential reuse with one Enter,csk config build-https add ... --token git-credentials,CSK_BUILD_HTTPS_TOKEN/CSK_BUILD_HTTPS_HOSTfor CI), plus pointers todocs/external-build-repositories.md.docs/skill-authoring.md: the schema v7 transport paragraph now covers both URL forms, explicit operator credential selection over either transport, and the mandatory.gitsuffix for HTTPS manifest URLs (301 +http.followRedirects=false->build_repository_source_unavailable).docs/troubleshooting.md:build_repository_credential_policy_invalidwith its three branches and a command each; the 301 no-suffix entry findable by both the git error text and the csk code; the Windows credential-store note (credential.credentialStore dpapi).docs/reference.md: the install matrix states compiled commands run only on macOS and Windows; on Linux the installer refuses before credentials or worker start.Review evidence
Board story docs-build-https: 3 content tasks, 7 review rounds (claude-opus-5, every error string re-verified against src/csk and every command against the tree's csk). No secrets in examples; file languages preserved.