Retire branches and decommission projects according to lifecycle policy.
Stale branches and inactive projects degrade navigation and access reviews. Schedule cleanup after milestones to keep the workspace auditable and scannable.
Branch lifecycle: archive
Retiring a branch in Studio is archive — hidden from the switcher and branch list; commit history retained server-side.
| Condition | Action |
|---|---|
Work promoted to default (main) | Archive feature branch |
| Experiment with no retention requirement | Archive after verification |
| Default branch | Cannot archive — promote replacement default first |
Archive procedure
- Branch switcher → View history & branches
- Select branch in the list
- Archive… → Confirm archive
No Unarchive in the UI. Treat archive as final for operational purposes.
Project lifecycle: delete
Projects are deleted, not archived. Deletion is irreversible — branches, content, members, publish configuration, and GitHub links are removed.
Pre-deletion checklist
- Confirm no active contributors
- Retire or redirect published URLs
- Export via Clone or GitHub sync if retention is required
Delete procedure
- Project row → Project settings → General
- Delete project → type project name → confirm
- Remove members whose access was limited to that project
Review cadence
Archive feature branches when work is on default and reviewed.
Governance for branch naming and lifetime: Branch Naming and Strategy.
Last updated on