auth login: origin-mismatch UI does not fire for env-only (MADTEA_URL) forge config #379

New issue

Closed

opened 2026-08-16 21:41:57 +00:00 by hexajon · 0 comments

hexajon commented

2026-08-16 21:41:57 +00:00

Owner

The origin-aware interactive auth login (branch fix/auth-login-origin-aware) compares the configured forge against the repo origin and warns on a mismatch. The configured forge comes from config.DetectURL, which reads the merged madtea.url git config and the origin remote, but NOT the MADTEA_URL environment variable.

So a forge configured purely via MADTEA_URL yields configuredForge="", and planLogin forces mismatch=false. A genuine env-forge-vs-origin mismatch is silently not surfaced.

Not a regression (the prior flow had no mismatch detection at all). Fix: have the mismatch detection also treat MADTEA_URL as a configured-forge source (resolve the configured forge through the same precedence the resolver uses), so env-configured users get the mismatch warning too.

The origin-aware interactive `auth login` (branch `fix/auth-login-origin-aware`) compares the configured forge against the repo origin and warns on a mismatch. The configured forge comes from `config.DetectURL`, which reads the merged `madtea.url` git config and the origin remote, but NOT the `MADTEA_URL` environment variable. So a forge configured purely via `MADTEA_URL` yields `configuredForge=""`, and `planLogin` forces `mismatch=false`. A genuine env-forge-vs-origin mismatch is silently not surfaced. Not a regression (the prior flow had no mismatch detection at all). Fix: have the mismatch detection also treat `MADTEA_URL` as a configured-forge source (resolve the configured forge through the same precedence the resolver uses), so env-configured users get the mismatch warning too.

hexajon referenced this issue

2026-08-17 04:57:07 +00:00

fix: MCP repo/init resolve the forge from a fixed launch dir + global default, not the working directory (second-forge ops break) #390

hexajon referenced this issue from a commit

2026-08-17 11:03:51 +00:00

fix(config): resolve the forge from the working context, not a stale global default

hexajon referenced this issue from a pull request that will close it,

2026-08-17 11:03:51 +00:00

fix(config): resolve the forge from the working context, not a stale global default #406

hexajon referenced this issue from a commit

2026-08-17 11:03:51 +00:00

test(setup): swap the #379 sample host codeberg.org to example.org