Archive a repository

Archive the experimental-ui repository today. Confirm the default branch has a recent tag, remove write access for external contractors, note any open issues or PRs that need follow-up, then set the repo to archived so it is read-only and add a pinned note in the org handbook explaining why it was archived and who to contact to restore it.

Before I archive experimental-ui, make sure reviewers can still find why it’s archived — bring the retirement rationale to the top, surface unresolved issues with suggested owners, show any deployments or hooks that must be disabled, and flag any ongoing forks or dependents that would cause a stakeholder to object.

I tried to archive experimental-ui but the CI integration still triggered a deploy right after I flipped the archive setting. I’m afraid archiving will break a downstream test or release pipeline we didn’t know about. What likely caused the integration to still run and what’s the safest immediate step so we can make the repo read-only without disrupting production pipelines?

We keep archiving repos only to restore them weeks later because someone on another team still relied on them. Where is our process failing: who should we consult before archiving and what quick signals (issues, dependents graph, recent deploys) will prevent needless restores and maintain credibility with other teams?