f7d5342c44
Five status-page workflows have been red on every cron tick (5x/hour)
since the 2026-05-06 GitHub org suspension. Symptom from the latest
run (run 8002):
url: api.github.com/repos/upptime/uptime-monitor/releases?per_page=1
data: { message: 'Bad credentials', status: '401' }
upptime fundamentally cannot work on this infra:
- upstream upptime/uptime-monitor action calls api.github.com on
every run to check its own version
- GitHub Molecule-AI org PAT is dead
- operator-host anonymous IP is rate-limited
- re-tokenizing with a personal PAT recreates the bot-ring shape
that triggered the original suspension (memory:
feedback_github_botring_fingerprint)
Move the five workflow files to .github/workflows-disabled-post-suspension/
so Gitea Actions stops dispatching them. This eliminates the 5x/hour
red CI noise on dashboards and stops paging on a known-impossible run.
Replacement plan: external uptime monitor (StatusPage.io, BetterStack,
healthchecks.io). RFC follow-up filed separately on internal#.
Files moved (no functional change to YAML):
- uptime.yml
- response-time.yml
- graphs.yml
- summary.yml
- static-site.yml
Plus a README explaining why under the new dir.
Rollback: git mv them back if upptime ever becomes runnable again.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
567 B
YAML
27 lines
567 B
YAML
name: Summary CI
|
|
on:
|
|
repository_dispatch:
|
|
types: [summary]
|
|
schedule:
|
|
# Daily summary of past-day uptime posted to the README badges.
|
|
- cron: "0 0 * * *"
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
release:
|
|
name: Generate README + summary
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0
|
|
- uses: upptime/uptime-monitor@v1.41.0
|
|
with:
|
|
command: "readme"
|
|
env:
|
|
GH_PAT: ${{ secrets.GH_PAT || secrets.GITHUB_TOKEN }}
|
|
|
|
permissions:
|
|
contents: write
|
|
issues: write
|