Skip to content

MiniCon SrcMgr 0.0.8

Choose a tag to compare

View all tags
@mgttt mgttt released this 28 Oct 08:10
· 6 commits to main since this release
v0.0.8
926e63a

MiniCon SrcMgr 0.0.8

Development source checkpoint. GitHub supplies the tagged source archives; no executable or portable ZIP is distributed with this release. The first qualified runnable Windows beta remains the 0.1.0 target.

Clone and remote configuration

  • clone <url> <destination> [--branch N] [--depth N] reviews the transport, an absolute destination, an empty or absent target, the branch name and the depth before any transfer.
  • Clone runs with --no-checkout, so no repository-configured filter executes before the downloaded repository is reviewed and trusted. Checkout is a separate, later decision.
  • A nonempty destination is refused with its contents untouched; a failed transfer leaves whatever Git wrote in place so it can be inspected instead of being deleted.
  • HTTP, ext::, unknown schemes, spaces and control characters are refused before Git runs.
  • remote <worktree> add|set-url|rename|remove ... prints a credential-free preview of the local effect and writes nothing unless --yes is present.
  • Remote names are checked with Git's own ref rules; unrelated configuration keys are preserved; removing a remote never touches the server repository.
  • After a write the command reports that the repository trust fingerprint changed, so the next repository action requires a fresh review.
  • Remote observation from 0.0.7 remains: redacted listing and refspecs, upstream distance, explicit fetch with per-ref results and cancellation.

The window still has no Clone form or Remotes surface; those, plus pull and push, are 0.0.9 scope in the roadmap.

Verification

Selected checks with MinGit 2.56.0 through SRCMGR_TEST_GIT:

  • srcmgr-git: 33 library cases, 3 clone fixtures and 3 remote-edit fixtures pass. The clone cases prove an unchecked-out worktree with resolved main, a preserved nonempty target, and refused transport/options that create nothing. The edit cases prove add/set-URL/rename/remove effects, preservation of an unrelated key, and byte-identical configuration after every refusal.
  • srcmgr-cli: 2 clone cases pass. A clone prints the deferred-checkout review and leaves no working file; an add without --yes changes no configuration, and with --yes writes the remote and reports the trust change.
  • Affected Clippy is clean and python scripts/check_docs.py passes.

Known limits

No binary, installer or signed package is produced or published. Authenticated HTTPS/SSH helper, askpass and host-key paths remain BLOCKED without a controlled fixture host; local paths are used for ref semantics only and are not authentication evidence.

There is no window Clone form, no Remotes editing surface, no pull, push or upstream write, no one-use confirmation ticket for a configuration write (the CLI requires the explicit --yes and the preview is printed), no persisted fetch time and no live in-window progress. No native, reference-host, accessibility, CJK/clipboard or long-session qualification is claimed.

See the tagged execution plan, delivery contract and developer build instructions. Report reproducible issues through GitHub Issues without credentials or private repository content.

Assets 2
Loading