fix: stop mike from writing symlinks into gh-pages, breaking Pages deploy - #18
Merged
Merged
Conversation
…ploy
GitHub's own automatic Pages build-and-deploy (triggered whenever
gh-pages is pushed - a separate workflow from this repo's docs.yaml)
started rejecting every deploy with "Artifact could not be deployed...
content does not contain any hard links, symlinks". mike's default alias
type ("symlink") is exactly that: the "latest" alias is a literal
filesystem symlink committed into gh-pages, which actions/deploy-pages
now refuses outright.
--alias-type redirect switches it to mike's own supported alternative: a
small HTML redirect page instead of a symlink, functionally identical for
visitors. Verified against the installed mike CLI (mike deploy --help
lists alias-type as one of symlink/copy/redirect, default symlink).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Summary
GitHub's own automatic Pages build-and-deploy (the
pages-build-deploymentworkflow, triggered whenevergh-pagesis pushed - separate from this repo's owndocs.yaml) has been failing every run:docs.yamlruns./gradlew publishDocs, which shells out tomike deploy --push --update-aliases <tag> latest.mike's default alias type issymlink- thelatestalias is committed intogh-pagesas a literal filesystem symlink, whichactions/deploy-pagesnow rejects outright.Fix
Added
--alias-type redirectto themike deployinvocation - mike's own built-in alternative that writes a small HTML redirect page instead of a symlink for the alias. Functionally identical for anyone visiting/latest/, just no symlink in the tree.Verified against the installed
mikeCLI:mike deploy --helplists--alias-type {symlink,copy,redirect}(defaultsymlink).Note
The next successful
docsworkflow run will redeploygh-pageswith the alias rebuilt as a redirect page instead of a symlink, which should let GitHub's automatic Pages deployment succeed again. No repo settings changes needed.🤖 Generated with Claude Code