flake: drop forgejo-mcp and the omp-forgejo wrapper #109

Merged

yuris merged 1 commit from drop-forgejo-mcp into main

2026-08-22 05:23:01 +00:00

yuris commented

2026-08-22 05:17:47 +00:00

Owner

Never used. Every Forgejo call this repo has made went through curl against the REST API with a secretspec-provided token, so the MCP server sat in the dev shell doing nothing.

Removed:

the omp-forgejo wrapper derivation — its only job was re-execing omp under secretspec
pkgs.forgejo-mcp from the default shell's packages
the agents: omp-forgejo line from the shell banner
.omp/mcp.json, which registered the server. Untracked, so it leaves no trace in the diff, but leaving it would point a config at a command the shell no longer provides.

Nothing installs omp itself — the wrapper assumed an ambient one, and that was the last omp reference in the flake.

Removals only, no reformatting. nix fmt wanted to reindent the unrelated check derivation (the file was never alejandra-clean, and CI only format-checks Lua); I reverted that and kept the diff to the four deletions.

Verified with nix flake check (all checks passed) and by entering the shell with env -i, where the resulting PATH carries zero forgejo entries. Worth noting the obvious trap: checked from an ordinary terminal, command -v forgejo-mcp still finds it — the stale direnv profile has it — so the clean-parent check is the one that means anything.

Never used. Every Forgejo call this repo has made went through `curl` against the REST API with a secretspec-provided token, so the MCP server sat in the dev shell doing nothing. Removed: - the `omp-forgejo` wrapper derivation — its only job was re-execing `omp` under secretspec - `pkgs.forgejo-mcp` from the default shell's packages - the `agents: omp-forgejo` line from the shell banner - `.omp/mcp.json`, which registered the server. Untracked, so it leaves no trace in the diff, but leaving it would point a config at a command the shell no longer provides. Nothing installs `omp` itself — the wrapper assumed an ambient one, and that was the last `omp` reference in the flake. **Removals only, no reformatting.** `nix fmt` wanted to reindent the unrelated `check` derivation (the file was never alejandra-clean, and CI only format-checks Lua); I reverted that and kept the diff to the four deletions. Verified with `nix flake check` (all checks passed) and by entering the shell with `env -i`, where the resulting PATH carries **zero** forgejo entries. Worth noting the obvious trap: checked from an ordinary terminal, `command -v forgejo-mcp` still finds it — the stale direnv profile has it — so the clean-parent check is the one that means anything.

yuris added 1 commit

2026-08-22 05:17:48 +00:00

flake: drop forgejo-mcp and the omp-forgejo wrapper

ci / ci (pull_request) Successful in 21s

Details

conformance / conformance (v1) (pull_request) Successful in 2m5s

Details

conformance / conformance (v2) (pull_request) Successful in 2m23s

Details

79387e53fd

Never used. Every Forgejo call this repo has made went through curl against the
REST API with a secretspec-provided token, so the MCP server was a dependency
that shipped in the dev shell and did nothing - it pulled forgejo-mcp and a
wrapper whose only job was to re-exec omp under secretspec.

The local .omp/mcp.json that registered the server is deleted too. It was
untracked, so it leaves no trace here, but leaving it would have pointed a
config at a command the shell no longer provides.

Nothing installs omp itself; the wrapper assumed an ambient one, which is the
last omp reference in the flake.

The shell is otherwise untouched - verified by evaluating with a clean parent
environment, where the new PATH carries no forgejo entry, rather than from this
terminal, whose stale direnv profile still has both and reports them present.

yuris merged commit e2adeb0b46 into main

2026-08-22 05:23:01 +00:00

yuris referenced this pull request from a commit

2026-08-22 05:23:02 +00:00

flake: drop forgejo-mcp and the omp-forgejo wrapper (#109)