chore: remove uptime monitoring (moved to StarTrail-org/status)#82
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Monitoring moved to a dedicated Upptime repo at StarTrail-org/status. The old setup with a `status` branch in this repo didn't work because Upptime's summary generator queries the default branch for commit history, not the data branch. Removes: uptime workflows, .upptimerc.yml, status-site/. Keeps: web/lib/uptime.ts (may be repointed to the new repo later).
andylizf
force-pushed
the
chore/remove-uptime-from-main
branch
from
91e973a to
ea8de93
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
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.
Summary
.upptimerc.yml,status-site/web/lib/uptime.ts(can be repointed later if the website needs it)The old setup with a
statusbranch didn't work because Upptime queries the default branch for commit history — a hard-coded assumption with no config override.