commit - 25b93c9f8a5de7388b1511bb141c781c89e97e89
commit + 6ba38ae10335c72e26d9cebfa9a7d473742b2a47
blob - 6227dc17ae6320be5f0bf3a3ce440aeb7d26cbd6
blob + ec93827f5e49d90529a215fda6d88b9f8f3170e8
--- docs/make.jl
+++ docs/make.jl
],
)
+# DocumenterVitepress has the code for this (writer.jl, `touch(...,
+# "final_site", ".nojekyll")`) but it's commented out in the installed
+# version (0.3.5) — confirmed by reading the package source, not assumed
+# — so gh-pages currently has no .nojekyll at all. Nothing has broken
+# from this yet (verified: the live site serves correctly), but GitHub's
+# default Jekyll processing on a branch-based Pages deploy silently
+# ignores any path starting with `_`, which is exactly the kind of thing
+# a future Vitepress internal-asset naming convention could introduce —
+# added here rather than relying on that staying true by luck. One file
+# per built base's own root (`docs/build/<n>/`, one per version — "1" for
+# "dev" right now, more once tags exist) since that's what deploydocs
+# actually publishes as each version's own directory in gh-pages.
+for dir in filter(isdir, readdir(joinpath(@__DIR__, "build"); join=true))
+ isfile(joinpath(dir, "index.html")) && touch(joinpath(dir, ".nojekyll"))
+end
+
DocumenterVitepress.deploydocs(;
repo="github.com/Richard7987/AsteroidPipeline.jl",
target=joinpath(@__DIR__, "build"),