Repository navigation
Run station freshness monitoring independently of deployment CI - #65
Merged
Merged
Conversation
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
1 participant
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.
The station freshness monitor checks the deployed endpoint. Running it on a source push can fail before that version is deployed and cause Railway wait-for-CI to skip the deployment. Keep hourly monitoring and workflow_dispatch; run the monitor explicitly after deployment verification.
Validation: dashboard PR #64 passed build, 68 .NET tests, 7 JavaScript tests, Docker build, CodeQL and NuGet audit. This change removes only the premature push trigger.