Honor managed package config when installing by repo target

[Copilot]

eget install <owner>/<repo> was bypassing packages.<name> config entries even when that repo was already declared in eget.toml. As a result, installs could skip configured package/global defaults such as the target directory.

• Install request resolution

  • Extend install target lookup to resolve managed package config by matching the requested repo against packages.<name>.repo, not just the package name.
  • Preserve existing behavior when there is no unique managed package match.

• Config application

  • Reuse the matched package section when merging install options, so repo-based installs inherit the same config as name-based installs.
  • This makes package-specific fields like target, tag, and other merged defaults apply consistently for both:
    • eget install gomi
    • eget install babarot/gomi

• Regression coverage

  • Add a focused test for a config like:

[global]
target = "~/.local/bin"

[packages.gomi]
repo = "babarot/gomi"
target = "~/managed/bin"
tag = "v1.6.3"

• The new coverage asserts that installing babarot/gomi uses the managed package config and does not fall back to the global target.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/babarot/gomi/releases/latest
  • Triggering command: /tmp/eget-test /tmp/eget-test install --quiet babarot/gomi (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR fixes install-option resolution so eget install <owner>/<repo> correctly reuses an existing managed package entry ([packages.<name>]) when that entry’s repo matches the requested repo target. This makes repo-based installs inherit the same package-specific defaults (e.g., target, tag) that previously only applied when installing by package name.

Changes:

• Extend install target lookup to match managed packages by packages.<name>.repo when the CLI target is a repo.
• Reuse the matched package section when merging install options, so repo installs inherit managed package settings.
• Add a regression test ensuring repo installs prefer managed package target over global.target.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
internal/app/install.go	Adds repo-to-managed-package matching and uses the matched package section when resolving install options.
internal/app/install_test.go	Adds a regression test verifying managed package config is honored when installing by repo target.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.