[triage-generated] [bug] Repo was archived causing mass-close of all issues - add safeguard #1472

Closed
opened 2026-03-24 22:38:59 +00:00 by Timmy · 1 comment
Owner

Bug

At 2026-03-24 ~21:53 UTC the repo was archived, which auto-closed all 1463 issues. This wiped the entire backlog.

Root Cause

Unknown - need to investigate which script or loop archived the repo. Likely a dev loop cycle that ran a PATCH with archived:true.

Acceptance Criteria

  1. Root cause identified
  2. Safeguard: no automated script should be able to archive the repo
  3. The Timmy API token should not have admin/archive permissions

Priority: P1

## Bug At 2026-03-24 ~21:53 UTC the repo was archived, which auto-closed all 1463 issues. This wiped the entire backlog. ## Root Cause Unknown - need to investigate which script or loop archived the repo. Likely a dev loop cycle that ran a PATCH with archived:true. ## Acceptance Criteria 1. Root cause identified 2. Safeguard: no automated script should be able to archive the repo 3. The Timmy API token should not have admin/archive permissions ## Priority: P1
Author
Owner

Closing during Gitea sweep: this repo is archived/frozen and no longer the active execution surface. Follow-on work belongs in the current canonical repos rather than keeping stale queue state alive here.

Closing during Gitea sweep: this repo is archived/frozen and no longer the active execution surface. Follow-on work belongs in the current canonical repos rather than keeping stale queue state alive here.
Timmy closed this issue 2026-04-05 00:13:51 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1472