Repository navigation
chore: add GitHub Pages deploy workflow and docs - #63
Merged
theghost1980 merged 1 commit intoFeb 8, 2026
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
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.
Motivation
basefor production builds.READMEso repo owners can enable Pages and troubleshoot common issues.Description
.github/workflows/deploy-pages.ymlthat runs onpushtomainandworkflow_dispatch, installs dependencies, runsnpm run typecheckandnpm run build, and publishes thedistartifact via the official Pages actions withpages: writeand proper concurrency.vite.config.tsto setbasedynamically duringbuildusing theGITHUB_REPOSITORYenv var (computed as/${repoName}/) while keeping local dev usingbase: '/'.README.mdwith aDeploy (GitHub Pages)section describing how to enable Pages, the expected URL (https://<OWNER>.github.io/<REPO>/), why the Vitebaseis needed, and short troubleshooting steps.Testing
npm run buildlocally, which executestsc -b && vite build, and the build completed successfully.distoutput was generated without errors (Vite reported build success).Codex Task