feat(vcs): commits pushed to git main come into vcs
Radin committed
- Author
- Radin · radin@coline.appOct 28, 2026 at 01:41
- Committer
- Radin · radin@coline.appOct 28, 2026 at 01:41
- Parents
- b6433e086072
feat(vcs): commits pushed to git main come into vcs Teams can use git and vcs on the same project. On Upstream, a push to the repository (Upstream's pushedAt, or a git view push that finds git main moved) makes the project fetch git main's new commits like a git client and bring them in: - vcs main where git main was: a version per first-parent commit, with its message and author, already in git (the version is that commit). - vcs landed meanwhile: one version merging them, pushed to git as a merge commit of both lines. - Private paths stay as they were. Conflicts, commits into private paths, force pushes and pushes over 32 MB pause the view with the reason. vcs-core reads git packs (deltas included) and turns git trees into vcs trees exactly as vcs import does. Repository answers are cached 10 s, so a push shows up in about 3-10 s. Live on git.coline.app: a push came in as its own commit, and a push racing a vcs land became a merge commit with both files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 files changed+811−17