Expand description
Defines basics outline of a VCS repo and the queries vcsq is meant to handle. Provides the traits any driver a particular brand of VCS must implement.
Structs§
- Ancestor
Ref - History
Ref - Single point in time in the Repo’s history.
Enums§
Constants§
Traits§
- Driver
- Repo-specific questions any VCS should be able to answer.
- Validator
- Generic questions a VCS driver should be able to answer: is the VCS program even available on this system? Does a directory even look like a valid VCS?.
Type Aliases§
- History
RefId - VCS repo’s canonical, machine-generated identifier describing a reference-point in its history (eg: branch or tag in git, bookmark in jj).
- History
RefName - VCS repo’s human-readable identifier describing a reference-point in its history (eg: branch or tag in git, bookmark in jj).
- Query
Dir - The local repository a VCS query will center around.
- VcsAvailable
- Proof of underlying VCS’s existence on the current system (typically –version output).