During Gitea storage migration (RWX → RWO), the first migration attempt failed because we didn't verify the rsync completed correctly before switching over.
Problem / Observation
Data migrations are risky operations. The first attempt caused downtime because:
rsync ran without verification
We switched Gitea to the new PVC before confirming data was present
Gitea showed "repository cannot be read" errors
Suggested Improvement
Create a skill or checklist for data migrations that enforces:
Pre-migration: Document what data must exist after migration
Migration: Run copy with verbose logging
Verification: Check specific files/directories exist before proceeding
Cutover: Only switch after verification passes
Rollback plan: Keep old storage until new is confirmed working
Affected Files
skills/data-migration/SKILL.md (new)
## Context
During Gitea storage migration (RWX → RWO), the first migration attempt failed because we didn't verify the rsync completed correctly before switching over.
## Problem / Observation
Data migrations are risky operations. The first attempt caused downtime because:
1. rsync ran without verification
2. We switched Gitea to the new PVC before confirming data was present
3. Gitea showed "repository cannot be read" errors
## Suggested Improvement
Create a skill or checklist for data migrations that enforces:
1. **Pre-migration**: Document what data must exist after migration
2. **Migration**: Run copy with verbose logging
3. **Verification**: Check specific files/directories exist before proceeding
4. **Cutover**: Only switch after verification passes
5. **Rollback plan**: Keep old storage until new is confirmed working
## Affected Files
- skills/data-migration/SKILL.md (new)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
During Gitea storage migration (RWX → RWO), the first migration attempt failed because we didn't verify the rsync completed correctly before switching over.
Problem / Observation
Data migrations are risky operations. The first attempt caused downtime because:
Suggested Improvement
Create a skill or checklist for data migrations that enforces:
Affected Files