The strategy_lab_pro service in tranquil-wholeness production has the repository connected but no branch set, and we deploy from GitHub automatically only when commits are pushed to a service's connected branch. So a merge of #84 into feat/beta-customers has no branch trigger to deploy that service.

None of the services in the novanexus workspace are connected to feat/beta-customers. The other services that use this repository are all connected to a different branch, so a push to feat/beta-customers does not match any of their triggers. We have not changed any settings or started any deployments.

Thank you. Since this is a production merge decision, could a Railway team member verify the actual configuration and confirm whether there are any other deploy triggers, GitHub App mechanisms, or pending deployments that could deploy feat/beta-customers despite the missing branch connection? Please do not change any settings or start a deployment.

We checked the live configuration again, and a merge of #84 into feat/beta-customers has nothing on our side that would deploy it. We only deploy from GitHub automatically when commits are pushed to a service's connected branch. The strategy_lab_pro service in tranquil-wholeness production has the repository connected but no branch set, and there are no unapplied changes in that environment that would add one.

No other service in the novanexus workspace is connected to feat/beta-customers. The other services built from NovaneHk/strategy_lab_pro all watch a different branch. None of them uses image auto-updates, and nothing is building, queued or deploying anywhere in the workspace right now.

The one thing this doesn't cover is a deploy started through our CLI or API by your own tooling, such as a GitHub Actions workflow. That lives in your repository, not in our service configuration. We have not changed any settings or started any deployments.