One working tree, two version control systems, and why we stopped, sgit.ai case study

How this site was developed for 76 releases in a single folder that was both an sgit vault and a git repository (the .gitignore boundary, why the encrypted ref always looked dirty to git (fresh AES-GCM IVs), the ordering rule) and why the vault mirror was retired and purged: no reader, no published read key, 91% of the repository, and seven releases shipped without it before anyone noticed.

Page: https://sgit.ai/case-studies/one-tree-two-remotes.html↗

Home↗ / Case studies↗ / One tree, two remotes