chore(cli): make web staging opt-in - #153
Merged
nkavian merged 1 commit intoOct 2, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
nkavian
force-pushed
the
chore/explicit-skill-staging
branch
from
October 2, 2026 21:41
b205e05 to
30683ed
Compare
nkavian
changed the title
nkavian
force-pushed
the
chore/explicit-skill-staging
branch
from
October 2, 2026 21:56
30683ed to
65a7aba
Compare
nkavian
force-pushed
the
chore/explicit-skill-staging
branch
from
October 2, 2026 22:02
65a7aba to
0ff2803
Compare
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
2 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.
Problem
Some InFlow developers want builds to refresh the sibling server's website assets; others want their server checkout left untouched.
Change
Keep web staging in
pnpm build, but requireINFLOW_WEB_STAGING=1. Thepnpm stage:webcommand runs the same step independently. It uses the existing sibling destination and skips copying when that destination is absent.No release sequencing or version-validation requirements are introduced.