Selected portable imports
Encrypted personal GitHub / GitLab.com connections support bounded selected imports. Private all-ref/history/LFS/metadata fidelity requires its own owned proofs.
GOLF Your setup / Connect or migrate
Bring the code. Preserve the meaning.
Golf has bounded provider connections and source imports; complete migration requires verified identities, permissions, history and collaboration fidelity.
Developer preview · capability review October 14, 202601 / CURRENT SLICES
Importing Git is one part of migration.
The retained hosted demo includes pinned upstream repositories with original authorship and history.
Native demo recipe
Alchemy seeds pinned upstream repositories through the supported Artifacts path, with recorded ownership and explicit public publication. Fixture provisioning is not a universal end-user importer.
Forgejo transition
Fresh portable installs use Forgejo. Import acceptance must verify private collaboration and identity data, not only Git content.
02 / ACCEPTANCE
Check more than the default branch.
A successful clone does not establish full application fidelity.
Identity and authority
Map users, organization/team roles, deploy keys and grants. Preserve current authorization without merging identities based on email alone.
Collaboration and assets
Compare PR/review state, issues, attachments, labels, releases, LFS and hidden refs. Missing private data must remain a migration blocker.
Cutover and recovery
Drain writers, use fresh supported targets, verify final delta and rollback. Never swap databases across incompatible providers or edit the live forge directly.
Make your first move.
Explore the hosted public repository, request enrollment for private workflows, or start your own portable installation.