Repository navigation
Host the Floor Plan Digitizer at /floorplantool/ (unlisted internal t… - #6
Merged
Merged
Conversation
…ool) Pull i-kumar/floorplandigitizer in as the git submodule `floorplantool/` and build it as a separate Vite app (base /floorplantool/) after the client build, copying its dist into client/dist/floorplantool so the GitHub Pages artifact serves it next to the site. Nothing on the site links to it on purpose. A submodule pointer bump on main redeploys it; the Build-and-Test workflow builds it on PRs too. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Pull i-kumar/floorplandigitizer in as the git submodule
floorplantool/and build it as a separate Vite app (base /floorplantool/) after the client build, copying its dist into client/dist/floorplantool so the GitHub Pages artifact serves it next to the site. Nothing on the site links to it on purpose. A submodule pointer bump on main redeploys it; the Build-and-Test workflow builds it on PRs too.