GoLand module proxy configuration lacks per‑module override for private repositories

GoLand module proxy configuration lacks per‑module override for private repositories

The goal is to prevent accidental exposure of private Go modules when a public proxy is configured in GoLand’s global module proxy setting.

Currently GoLand exposes only a single "Go module proxy" field under Settings > Go > GOROMOD > Module Proxy, with no way to specify different proxies for individual modules or to suppress proxy usage for private dependencies. The IDE does not emit a warning or log entry when a private module is resolved through the public proxy, and it is unclear whether the vendor command or module refresh respects a per‑module GOPROXY=off override.

• Does GoLand provide a mechanism to define per‑module proxy rules or to disable the proxy for specific private modules?
• Can the IDE be configured to emit a warning or log entry when a private module is resolved via the configured public proxy?
• Is there a setting that ensures the vendor operation or module refresh bypasses the public proxy for private dependencies without affecting other modules?