When installing an extension, the CLI must to select the correct binary to download for the machine (see the installBin function).

By default, the CLI will download a binary matching the current machine's architecture.

If a suitable binary isn't available, the CLI outputs an error, directing the user to create an issue on the extension's repository:

if asset == nil {
	return fmt.Errorf(
		"%[1]s unsupported for %[2]s. Open an issue: `gh issue create -R %[3]s/%[1]s -t'Support %[2]s'`",
		repo.RepoName(), platform, repo.RepoOwner())
}

The issue this creates isn't very clear or helpful. It isn't obvious where it is coming from, or what you need to do.

I would propose that we create that issue with a body, e.g.:

This GitHub CLI extension does not support the %[2]s architecture. I tried to install it on a %[2]s machine, and it failed due to the lack of an available binary. Would you be able to update the extension's build and release process to include the relevant binary? For more details, see https://docs.github.com/en/github-cli/github-cli/creating-github-cli-extensions.

This issue body was generated automatically by the GitHub CLI.

Related to #9592.