Skip to content

chore: parameterize base href for deployment and update related scripts#173

Merged
sinedied merged 2 commits into
microsoft:mainfrom
rossboast:parameterise-base-href
Jan 22, 2026
Merged

chore: parameterize base href for deployment and update related scripts#173
sinedied merged 2 commits into
microsoft:mainfrom
rossboast:parameterise-base-href

Conversation

@rossboast

Copy link
Copy Markdown
Contributor

Parameterize the base href to enable the moaw platform to be more readily hosted in other repositories.

@rossboast

Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree company="Microsoft"

@sinedied sinedied left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@sinedied
sinedied merged commit ef8b5c4 into microsoft:main Jan 22, 2026
2 checks passed
@sinedied

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 1.6.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

cmaneu pushed a commit that referenced this pull request Jun 10, 2026
PR #173 replaced runtime hostname-based base href detection with a
build-time hardcoded BASE_HREF, which forced the single deployed
artifact to always use /moaw/. This broke serving from the moaw.dev
custom domain (served at root /), where assets and routes resolved to a
non-existent /moaw/ path.

Restore the runtime .github.io detection so the same build works from
both moaw.dev (/) and *.github.io/moaw/ (/moaw/), while still
parameterizing the sub-path value via BASE_HREF (defaulting to /moaw/)
so the platform can be hosted in other repositories.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants