Skip to content

deploy.yml: only run on paths ci-deploy.sh actually touches - #6

Merged
sandamond merged 1 commit into
masterfrom
deploy-path-filter
Sep 2, 2026
Merged

deploy.yml: only run on paths ci-deploy.sh actually touches#6
sandamond merged 1 commit into
masterfrom
deploy-path-filter

Conversation

@sandamond

Copy link
Copy Markdown
Owner

Observed in the wild: merging the doc-only #5 still triggered a full deploy.yml run, which restarted tproxy-server and tproxy-keys and dropped every active family session, for a change that touched only deploy/CI.md. Adds a paths: filter matching exactly what deploy/ci-deploy.sh's two update scripts rebuild — relay sources, keys-panel/, deploy/update-relay.sh, and deploy.yml itself (so edits to the workflow get validated by actually running it).

🤖 Generated with Claude Code

The first two real merges to master proved this needed: a doc-only PR
(#5) still triggered a full deploy, restarting tproxy-server and
tproxy-keys - and therefore dropping every family member's live session -
for a change that couldn't possibly affect either binary. Scope the
trigger to what deploy/ci-deploy.sh's two update scripts actually rebuild:
the relay module's sources, keys-panel, and the update script itself, plus
this workflow file so edits to it get validated by actually running.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@sandamond
sandamond merged commit 247d23c into master Sep 2, 2026
3 checks passed
@sandamond
sandamond deleted the deploy-path-filter branch September 2, 2026 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant