Migration notes: Subversion to Git

A repository conversion can preserve files and commit history, but the team also needs a new operating model for distributed changes, review and release references.

Clean the source history

Map Subversion usernames to stable author identities, identify trunk, branches and tags, and remove generated binaries that should not enter every clone. Rehearse the conversion and compare representative revisions before freezing writes.

Define the shared workflow

Choose the authoritative remote, branch naming and merge policy before inviting routine commits. Keep release tags immutable and document when a rebase is acceptable on unpublished work.

Verify the cutover

Freeze Subversion, perform the final incremental import and compare tree hashes, tags and recent history. Make the old repository read-only with a clear pointer to Git rather than leaving two writable sources.