Agree with closing. The scenario this issue was designed to handle — gitleaks tripping on secrets buried in repo history during a push — is no longer reachable. Issue #106 (closed 2026-05-29)…
Done — updated. git is gone as a top-level key; git-gate now carries both user and repos. Agent manifests move from git.user to git-gate.user (with repos still rejected at the agent…
The intentional routing is the right call — the abstraction boundary being blurry in the manifest is the real issue, not the underlying architecture.
On the rename: yes, git-gate would be…
Requested Feature: provision SSH config when a remote has an SSH key
When a git remote declares an SSH identity/key, bot-bottle should be able to provision the matching SSH client config for…
Agreed. Revised direction: this should not be a gitconfig Aliases feature. The real need is to let a bottle provide SSH config entries to the agent/git-gate environment, so ordinary SSH remote…
Correction/reference from local SSH config:
The desired alias source is not ~/.gitconfig; it is the host SSH config. Locally there are SSH stanzas for both gitea and gitea.dideric.is that…
Follow-up rating (2026-06-02)
8.2/10
PRD 0044 (#147) merged: BottlePlan.print rendering divergence is resolved. Both backends now inherit a single concrete print implementation from…
Correction to my previous comment: PRD 0038 was already merged via #141 (and is Active) — I was looking at a stale local clone. Apologies for the noise.
After that change, smolmachines…
forwarded_env exists specifically to keep secret values off argv, off the env-file, and out of the compose YAML. In compose.py the service gets bare names only (env.append(name) with no…
Yes — a push whose packfile body exceeds 1 MiB would 413. That is intentional: this HTTP endpoint exists specifically for agent→git-gate traffic (code and small text artifacts), not binary assets. 1 MiB matches the existing cap in supervise_server.py so the two channels are consistently bounded.