Skip to content

Document Git Core operation contracts - #115

Merged
1lck merged 2 commits into
1lck:preview/0.3.0from
yangboxuan726:docs/git-core-operation-contracts
Aug 17, 2026
Merged

Document Git Core operation contracts#115
1lck merged 2 commits into
1lck:preview/0.3.0from
yangboxuan726:docs/git-core-operation-contracts

Conversation

@yangboxuan726

Copy link
Copy Markdown
Contributor

What changed

  • Add the active Git preflight, conflict-marker, and operation-state commands to the Rust Core command table.
  • Document their request fields, response fields, ordering, nullable values, and current semantics.
  • Add operationContinue, operationAbort, and operationSkip to the git.write operation list and describe their state-aware restrictions.

Why

The shared contract omitted commands and write operations already implemented by rust/lithe-core and consumed by the platform adapters. This update makes the contract match the protocol command enum, Rust request/response types, implementation, and tests without changing runtime behavior.

Validation

  • cargo test --manifest-path rust/lithe-core/Cargo.toml git_ (11 unit tests and 3 integration tests passed)
  • PowerShell command-name consistency check against rust/lithe-core/src/protocol/command.rs
  • git diff --check

./scripts/verify-shared-contracts.sh was not runnable on this Windows host because it requires zsh and /usr/bin/ruby; the only installed WSL distribution is docker-desktop.

@yangboxuan726
yangboxuan726 force-pushed the docs/git-core-operation-contracts branch from 99a504c to 446e369 Compare August 17, 2026 00:35
@yangboxuan726
yangboxuan726 marked this pull request as ready for review August 17, 2026 00:35
@yangboxuan726
yangboxuan726 requested a review from 1lck as a code owner August 17, 2026 00:35
@1lck
1lck merged commit 5892856 into 1lck:preview/0.3.0 Aug 17, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants