Document batched bootstrap tag support

ba85a15→main·

Soph·3mo ago·3 files·+7 added/-4 removed

Sessions

6ef2787ebf99View transcript

[?
Can you take a look at the go code (wasm) in /Users/soph/Work/entire/devenv/entire-io-worktree1 based a bit on that I wonder if something like this can be build:Codex·GPT-5.4·1 step](/content/gh/entireio/git-sync/session/019d6d29-8cf7-7fe3-adc9-8c3e4d9d5603#timeline-6ef2787ebf99/index.html)

Changes

3

• MREADME.md+2/-2

• docs

• Mbootstrap-batching.md+4

• Mbootstrap.md+1/-2

88 unmodified lines

89
90
91
92
93
92
93
94
95
96

88 unmodified lines

Current batching scope is intentionally narrow:

- protocol v2 only
- branch refs only
- no tags
- branch refs are batched
- optional create-only tags are pushed after branch batches complete
- temporary refs under `refs/gitsync/bootstrap/heads/`
- resume from existing temp refs is supported when they match a planned checkpoint

MREADME.md+2/-2

265 unmodified lines

266
267
268
269
270
271
272
273
274
275

265 unmodified lines

- consider tag creation after successful branch completion
- consider whether per-ref or per-branch parallelism is worth it

Progress:

- create-only tags are now pushed after successful branch batches complete

Phase D:

- only then consider using similar checkpoint batching ideas for non-empty target incremental relay

Mdocs/bootstrap-batching.md+4

168 unmodified lines

169
170
171
172
173
172
173
174
175

168 unmodified lines

- the current batched bootstrap path is intentionally narrow
- it requires source-side protocol v2 with fetch filters
- it supports branch refs only
- it does not support tags yet
- it batches branch refs and then optionally creates tags after the branch batches complete
- it resumes from an existing temp ref when that temp ref matches a planned checkpoint
- it uses temporary target refs under `refs/gitsync/bootstrap/heads/`

Mdocs/bootstrap.md+1/-2