You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before this fix, POST /projects/migrate compared old_project and new_project
with an exact string equality check, so "repo_name" vs "Repo_Name" bypassed
the skip guard and triggered a real migration, reintroducing the duplicate
project problem fixed in Gentleman-Programming#136.
- server.go: normalize both names via store.NormalizeProject before the
equality check; case-only differences now return status="skipped"
- _helpers.sh: lowercase detect_project output via tr '[:upper:]' '[:lower:]'
- session-start.sh: lowercase OLD_PROJECT at assignment
0 commit comments