The artifact hash prefix 4aa0 is ambiguous and might mean any of the following:
4aa0304fb07074c5847c33a72c70107d008aa5b0208441971d7a32662cd02eb2 -
- File internal/checkout/fork.go — part of check-in [425dd36e13] at 2026-10-13 06:14:52 on branch main — fix(checkout): pick the no-target update target as fossil does; read untagged check-ins as the default branch (#399) (user: [email protected], size: 7233) [annotate] [blame] [check-ins using]
4aa0f49ba429632056a89d3832bfbbac6da4eb0f93bc215197985676fb06c5ad -
- File
repo_sync.go
— part of check-in
[9776c25462]
at
2026-07-19 18:17:56
on branch trunk
— Remove unused CloneOpts.ProjectCode and ServerCode fields (#77)
Both were accepted by the public CloneOpts but never forwarded to the internal clone path, so setting either silently did nothing. The internal clone options struct has no matching fields at all, so wiring them would mean designing semantics first — is a caller- supplied code a validation assertion or an identity override? — and no caller has asked for either. Delete them rather than guess.
CloneResult.ProjectCode and CloneResult.ServerCode are unrelated and unaffected: they are populated from the internal clone's return value (the remote, via protocol negotiation), not from caller options, and continue to work exactly as before. Consistent with the same call made on UpdateOpts.Force. (user: [email protected], size: 6681) [annotate] [blame] [check-ins using]
- File
repo_sync.go
— part of check-in
[9776c25462]
at
2026-07-19 18:17:56
on branch trunk
— Remove unused CloneOpts.ProjectCode and ServerCode fields (#77)