Skip to content

MiniCon SrcMgr 0.0.7

Choose a tag to compare

View all tags
@mgttt mgttt released this 28 Oct 04:16
· 9 commits to main since this release
v0.0.7
b3321ee

MiniCon SrcMgr 0.0.7

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.

Remote observation and explicit fetch

  • Configured remotes are read from Git's machine output with fetch and push URL labels redacted; passwords, tokens in userinfo and URL query/fragment parts never reach a label.
  • Fetch refspecs are shown as configured rather than replaced by a branch selector.
  • The current branch's upstream and its distance (ahead/behind) come from the fetched tracking ref, not from live server truth.
  • fetch names exactly one remote and reports the old/new object ids Git actually updated. A remote that is configured as a mirror is refused before any transfer; prune and submodule recursion are not enabled implicitly.
  • Network work has its own deadline, bounded output, cooperative cancellation that terminates the owned process tree, and progress filtered to Git's transfer lines. Remote banners and URLs are excluded.
  • The window appends the upstream distance to the status line and binds f to a fetch of the upstream-named remote, otherwise the first configured remote; with no remote it explains instead of acting.
  • CLI for verification: remote <worktree> list [--json], remote <worktree> tracking [--json] and fetch <worktree> <remote> [--json].

Clone, remote configuration writes, pull, push and authenticated transports are not part of this checkpoint; they are allocated to 0.0.8 and 0.0.9 in the roadmap.

Verification

Selected checks ran against MinGit 2.56.0 through SRCMGR_TEST_GIT:

  • srcmgr-git: 31 library cases plus 4 new remote fixtures pass. The fixtures cover redaction and refspecs, a fetch that updates exactly the second copy's OID, an unknown remote refused before any transfer, and a mirror remote refused before any transfer. The ten status fixtures still pass.
  • srcmgr-ui: 94 library cases pass, including upstream-remote selection and the no-remote explanation.
  • srcmgr-cli remote test: the configured credential is absent from product output, the tracking ref equals the remote HEAD, tracking reports ahead 0 / behind 1, and an unknown remote leaves HEAD unchanged.
  • cargo clippy -p srcmgr-git -p srcmgr-ui -p srcmgr-cli --all-targets reports no warnings; 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; a local-path remote is used for ref semantics only and is never counted as authentication evidence.

The window has no dedicated Remotes surface, no per-remote selection, no clone, no pull or push, no persisted fetch timestamp and no live in-window progress (the CLI streams filtered progress). No native GUI remote journey, reference-host, accessibility, CJK/clipboard or long-session qualification is claimed; earlier scoped evidence keeps its original source and artifact identity under the 0.0.6 plan.

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