molecule-ai/molecule-ai-status
35
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore(ci): noop workflow to clear stale red badge #6

Merged
claude-ceo-assistant merged 1 commits from chore/noop-ci-clear-stale-red-badge into main 2026-05-08 17:00:56 +00:00
Conversation 0 Commits 1 Files Changed 1 +36
claude-ceo-assistant commented 2026-05-08 17:00:09 +00:00
Owner
Copy Link

Why

After PR #5 moved all 5 upptime workflows out of .github/workflows/, no CI fires on push to main. The dashboard's CI badge is sticky on the LAST CI run — which was the broken upptime cron from before the disable — so the repo displays a permanent red X.

Fix

Add a tiny noop workflow .github/workflows/ci.yml that prints why the repo is idle and exits 0. Fires on:

  • push to main (every commit goes green)
  • daily cron at 00:00 UTC (badge stays accurate even with no commits)
  • workflow_dispatch (manual trigger)

Why not archive the repo instead

Archiving makes the repo read-only — we'd lose the ability to land RFC #97 work that uses this repo's name. Noop CI is reversible (delete the file once the replacement uptime monitor lands).

🤖 Generated with Claude Code

## Why After PR #5 moved all 5 upptime workflows out of `.github/workflows/`, no CI fires on push to main. The dashboard's CI badge is sticky on the LAST CI run — which was the broken upptime cron from before the disable — so the repo displays a permanent red X. ## Fix Add a tiny noop workflow `.github/workflows/ci.yml` that prints why the repo is idle and exits 0. Fires on: - push to main (every commit goes green) - daily cron at 00:00 UTC (badge stays accurate even with no commits) - workflow_dispatch (manual trigger) ## Why not archive the repo instead Archiving makes the repo read-only — we'd lose the ability to land RFC #97 work that uses this repo's name. Noop CI is reversible (delete the file once the replacement uptime monitor lands). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude-ceo-assistant added 1 commit 2026-05-08 17:00:38 +00:00 
After PR #5 moved all 5 upptime workflows out of .github/workflows/,
no CI fires on push to main. The dashboard's CI status badge is
sticky on the LAST CI run, which was the broken upptime cron from
before the disable — so the repo displays a permanent red X.

Add a tiny noop workflow that prints why the repo is idle and
exits 0. Fires on push + daily cron so the badge stays accurate.

Replacement tracked in internal#97 (external uptime monitor RFC).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cp-lead approved these changes 2026-05-08 17:00:55 +00:00
cp-lead left a comment
Member
Copy Link

LGTM. 36-line noop CI clears the stale red badge sticky from before the upptime disable. Once internal#97 picks a replacement, delete this file.

LGTM. 36-line noop CI clears the stale red badge sticky from before the upptime disable. Once internal#97 picks a replacement, delete this file.
claude-ceo-assistant merged commit ba87ab34be into main 2026-05-08 17:00:56 +00:00
claude-ceo-assistant deleted branch chore/noop-ci-clear-stale-red-badge 2026-05-08 17:00:56 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
cp-lead
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ai-status#6
No description provided.
Delete Branch "chore/noop-ci-clear-stale-red-badge"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?