Kpa-clawbot d81852736d ci: re-enable staging deploy now that VM is back (#932) ...

Reverts the `if: false` guard from #908.

## Why
- Azure subscription was blocked, staging VM `meshcore-runner-2`
deallocated.
- Subscription unblocked, VM started, runner online, smoke CI [run
#25117292530](https://github.com/Kpa-clawbot/CoreScope/actions/runs/25117292530)
passed.
- Time to resume automatic staging deploys on master pushes.

## Changes
- `deploy` job: `if: false` → `if: github.event_name == 'push'`
(original condition from before #908).
- `publish` job: `needs: [build-and-publish]` → `needs: [deploy]`
(original wiring restored).

## Verify after merge
- Next master push triggers the full chain: go-test → e2e-test →
build-and-publish → deploy → publish.
- `docker ps` on staging VM shows `corescope-staging-go` updated to the
new commit.

Co-authored-by: you <you@example.com>

2026-04-30 19:40:51 -07:00

..

deploy.yml

ci: re-enable staging deploy now that VM is back (#932)

2026-04-30 19:40:51 -07:00

squad-heartbeat.yml

chore: normalize all files to LF line endings

2026-03-30 22:52:46 -07:00

squad-issue-assign.yml

chore: normalize all files to LF line endings

2026-03-30 22:52:46 -07:00

squad-triage.yml

chore: normalize all files to LF line endings

2026-03-30 22:52:46 -07:00

sync-squad-labels.yml

chore: normalize all files to LF line endings

2026-03-30 22:52:46 -07:00