fix: nginxaas static content is referenced in subdirectory#2163
Merged
Conversation
github-actions
Bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
During a recent refactor, it looks like references for this static content were changed, but the location wasn't adjusted to match the referenced location. This fixes that.
tstraley
force-pushed
the
nginxaas/static-assets-path
branch
from
July 21, 2026 18:24
0b440be to
16e4c60
Compare
github-actions
Bot
added
the
tooling
travisamartin
approved these changes
Jul 21, 2026
y82
approved these changes
Jul 21, 2026
lamATnginx
approved these changes
Jul 21, 2026
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
5 participants
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.
During a recent refactor, it looks like references for this static content were changed, but the location wasn't adjusted to match the referenced location. This fixes that.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩