ci(docs): deploy VitePress to GitHub Pages on push to main - #4
Merged
Conversation
- new: .github/workflows/docs.yml — build on PRs touching apps/docs (or CI/lockfile inputs), deploy on main pushes only. Uses the standard configure-pages → upload-pages-artifact → deploy-pages chain. - shared.ts: thread `base` through DOCS_BASE env var so production builds get '/Bridgent/' (the project page URL) while local dev/preview keep '/'. CI workflow sets the env explicitly. - apps/docs/public/.nojekyll: empty file so GitHub Pages serves VitePress's `_assets/` etc verbatim instead of running Jekyll. One-time repo setup the maintainer still has to do: Settings → Pages → Source = "GitHub Actions" If a custom domain (e.g. bridgent.ai) gets pointed at the page later, flip DOCS_BASE to '/' in the workflow and add CNAME in apps/docs/public.
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.
basethrough DOCS_BASE env var so production builds get '/Bridgent/' (the project page URL) while local dev/preview keep '/'. CI workflow sets the env explicitly._assets/etc verbatim instead of running Jekyll.One-time repo setup the maintainer still has to do:
Settings → Pages → Source = "GitHub Actions"
If a custom domain (e.g. bridgent.ai) gets pointed at the page later, flip DOCS_BASE to '/' in the workflow and add CNAME in apps/docs/public.