[chore] disable upptime workflows post-suspension (part of #2) #3

claude-ceo-assistant · 2026-05-08T01:09:13Z

2026-05-08 01:09:13 +00:00

Summary

Stop the bleeding. All 5 upptime-driven workflows in this repo fail every scheduled run with HTTP 401 from api.github.com post the 2026-05-06 GitHub org suspension. Move them to .github/workflows-disabled/ so Gitea Actions stops scheduling them while the replacement is built.

What changed

Moved graphs.yml, response-time.yml, static-site.yml, summary.yml, uptime.yml from .github/workflows/ to .github/workflows-disabled/.
Added a README in workflows-disabled/ explaining the move and linking #2.
Did NOT touch history/ (existing probe data — may migrate forward) or .upptimerc.yml (probe-list config — useful as input to the replacement).

Why move, not delete

If we ever roll back the replacement effort, git log is enough — but workflows-disabled/ is more discoverable than git archaeology for a future contributor wondering why this repo's CI is silent. Cost: 0 (Gitea Actions doesn't scan that directory).

Test plan

Confirm .github/workflows/ is empty after this PR — no scheduled runs after merge.
After merge, confirm zero new failed-run notifications over the next 24 hours.

Tracking

Replacement plan: #2
Out of scope: history migration, status-page rebuild, probe-list refactor.

Generated with Claude Code.

## Summary Stop the bleeding. All 5 upptime-driven workflows in this repo fail every scheduled run with HTTP 401 from `api.github.com` post the 2026-05-06 GitHub org suspension. Move them to `.github/workflows-disabled/` so Gitea Actions stops scheduling them while the replacement is built. ## What changed - Moved `graphs.yml`, `response-time.yml`, `static-site.yml`, `summary.yml`, `uptime.yml` from `.github/workflows/` to `.github/workflows-disabled/`. - Added a README in `workflows-disabled/` explaining the move and linking #2. - Did NOT touch `history/` (existing probe data — may migrate forward) or `.upptimerc.yml` (probe-list config — useful as input to the replacement). ## Why move, not delete If we ever roll back the replacement effort, `git log` is enough — but `workflows-disabled/` is more discoverable than git archaeology for a future contributor wondering why this repo's CI is silent. Cost: 0 (Gitea Actions doesn't scan that directory). ## Test plan - [x] Confirm `.github/workflows/` is empty after this PR — no scheduled runs after merge. - [ ] After merge, confirm zero new failed-run notifications over the next 24 hours. ## Tracking - Replacement plan: #2 - Out of scope: history migration, status-page rebuild, probe-list refactor. Generated with Claude Code.

claude-ceo-assistant added 1 commit 2026-05-08 01:09:13 +00:00

chore(ci): disable upptime workflows post-GitHub-suspension (closes part of #2 ) a94dcf212f

All 5 upptime-driven workflows (graphs / response-time / static-site /
summary / uptime) call api.github.com for releases lookup + issue
management + result commits. Post the 2026-05-06 GitHub org
suspension, no token in our org authenticates there anymore — every
scheduled run fails with HTTP 401 "Bad credentials".

Move the workflow files to .github/workflows-disabled/ so Gitea
Actions stops scheduling them. Adds a README explaining what
happened and pointing at #2 for the replacement plan
(Gitea-native uptime probe).

The history/ directory and .upptimerc.yml stay untouched — the
existing probe-list config is still useful as input to the
replacement; the historical JSON files are read-only data we may or
may not migrate forward.

Tracked: #2.

claude-ceo-assistant closed this pull request

2026-05-08 01:15:31 +00:00

infra-lead referenced this pull request

2026-05-08 23:55:05 +00:00

[migrate] Replace upptime with Gitea-native uptime probe (closes #2) #4