fix(gitlab): resolve tool options from config for aliased tools

[jdx]

Summary

• Fix api_url (and other tool options like version_prefix) not being respected when using tool_alias with gitlab/github/forgejo backends
• Three fixes:
  1. _list_remote_versions: Was using self.ba.opts() which for aliased tools doesn't have config-defined options. Now uses config.get_tool_opts().
  2. install_version_: Same issue — was using tv.request.options() which doesn't carry config options for aliased tools. Now uses config.get_tool_opts().
  3. strip_version_prefix: Was independently reading self.ba.opts(). Now takes opts as a parameter from the caller (which already has resolved opts).
  4. get_tool_opts: Was matching by ba.short only, which for aliased tools is the alias name (e.g., treesize), not the config key (e.g., gitlab-f-bibonne-treesize). Now resolves the alias via full() and tries the resolved short name first.

Fixes #8079

Verified

• mise ls-remote treesize correctly queries framagit.org (not gitlab.com) when using alias with api_url
• mise install treesize@1.0.0 correctly downloads from framagit.org
• Unit tests for strip_version_prefix pass

Test plan

• mise ls-remote treesize with aliased gitlab tool + custom api_url → queries correct instance
• mise install treesize@1.0.0 with aliased gitlab tool + custom api_url → installs from correct instance
• Unit tests pass (test_version_prefix_functionality)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes how GitHub/GitLab/Forgejo backends resolve per-tool options during version listing and installs, which can affect what URLs/tags are used for downloads. Scope is contained and covered by updated unit tests plus a new GitLab alias e2e regression test.

Overview
Fixes unified GitHub/GitLab/Forgejo backends to honor config-defined tool options when invoked via tool_alias (e.g., api_url, version_prefix, asset_pattern) for both ls-remote and installs.

Updates Config::get_tool_opts to resolve options by the backend’s resolved full name first (avoiding alias short-name misses), and threads resolved options through strip_version_prefix instead of having it read backend-local opts. Adds an e2e GitLab regression test ensuring ls-remote and mise x work through an alias.

^{Written by Cursor Bugbot for commit 8c3ba8e. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @jdx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug where custom tool options, particularly api_url, were being ignored when users leveraged tool aliases for Gitlab, GitHub, or Forgejo backends. The fix ensures that the system correctly consults the configuration for tool-specific options, thereby allowing aliased tools to function as expected with their defined settings. This improves the reliability and flexibility of tool management within the application.

Highlights

• Tool Option Resolution: Resolved an issue where tool options, such as api_url, were not correctly applied when using tool_alias with Gitlab, GitHub, and Forgejo backends.
• Configuration Lookup: Modified the _list_remote_versions function to explicitly retrieve tool options from the configuration using config.get_tool_opts(), aligning with the approach used by s3 and http backends.
• Fallback Mechanism: Implemented a fallback to self.ba.opts() if no specific tool options are found in the configuration for a given aliased tool.

Changelog

• src/backend/github.rs
  • Updated the _list_remote_versions function to correctly retrieve tool options from the application configuration, ensuring api_url and other settings are respected for aliased tools.

Activity

• A test plan was provided to verify mise ls-remote gitlab:FBibonne/treesize works with api_url set via tool_alias and to ensure existing GitHub/Gitlab/Forgejo backend tests pass.
• The pull request description indicates it was generated with Claude Code.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull request overview

Fixes unified Git backends (GitLab/GitHub/Forgejo) so tool options (e.g., api_url) are correctly resolved from config when using tool_alias, preventing unintended fallback to default hosts like gitlab.com.

Changes:

• Update _list_remote_versions to resolve tool options via config.get_tool_opts() for aliased tools
• Keep a fallback to self.ba.opts() when config has no tool options for the backend arg

---

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

[gemini-code-assist]

Code Review

This pull request correctly fixes an issue where tool options like api_url were not being respected for aliased tools in the GitHub, GitLab, and Forgejo backends. The change modifies _list_remote_versions to resolve tool options from the configuration, falling back to the backend arguments if not found. This aligns the behavior with other backends like s3 and http and correctly addresses the described problem. The implementation is clean and effective. Good work.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON, but a Cloud Agent failed to start.}

[github-actions]

Hyperfine Performance

mise x -- echo

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.9 x -- echo	21.6 ± 0.4	21.0	26.7	1.00
mise x -- echo	22.0 ± 1.7	21.2	53.1	1.02 ± 0.08

mise env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.9 env	21.1 ± 0.3	20.4	22.0	1.00
mise env	21.6 ± 1.1	20.8	31.2	1.02 ± 0.05

mise hook-env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.9 hook-env	21.7 ± 0.4	21.1	25.4	1.00
mise hook-env	22.2 ± 0.6	21.4	29.3	1.02 ± 0.03

mise ls

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.9 ls	19.8 ± 0.2	19.3	21.0	1.00
mise ls	20.1 ± 0.3	19.5	21.2	1.01 ± 0.02

xtasks/test/perf

Command	mise-2026.2.9	mise	Variance
install (cached)	124ms	120ms	+3%
ls (cached)	74ms	74ms	+0%
bin-paths (cached)	77ms	78ms	-1%
task-ls (cached)	534ms	541ms	-1%