bug: not all git remotes are called "origin"

[sbaildon]

Did you check docs and existing issues?

• I have read all the lazy.nvim docs
• I have searched the existing issues of lazy.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.9.0-dev-f43fa30

Operating system/version

macOS 13

Describe the bug

Actions involving plugin git repositories don't work after initial clone because lazy is hardcoded to look for a remote called "origin"

lazy.nvim/lua/lazy/manage/git.lua

Lines 198 to 200 in 0f713b2

	function M.get_origin(repo)
	return M.get_config(repo)["remote.origin.url"]
	end

I have a git config a custom remote name, which causes issues with updating, syncing etc.

[clone]
  defaultRemoteName = upstream

Steps To Reproduce

1. git config --global clone.defaultRemoteName upstream
2. ...install plugins with Lazy
3. Open neovim, <cmd>Lazy<cr>
4. C for Check
5. see an error like, ...l/share/nvim/lazy/lazy.nvim/lua/lazy/manage/task/git.lua:137: attempt to concatenate local 'origin' (a nil value)
6. revert to default origin git config --global --unset clone.defaultRemoteName

Expected Behavior

Lazy can update, sync, and check plugins without errors

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

[folke]

Haven't tested it, but this should fix it. Let me know if it doesn't

[sbaildon]

#5af9380 isn't a full fix, the check path fails to build the correct config key because clone.defaultRemoteName is a property of a global config, not a local repo

lazy.nvim/lua/lazy/manage/task/git.lua

Line 145 in 1407565

local origin = Git.get_origin(self.plugin.dir)

[folke]

sorry, but this is out of scope for lazy. I'm not going to spend more time on this. Not something a lot of people will use anyway

[lougreenwood]

I got hit by this issue yesterday when setting up AstroNvim with a local copy of their AstroCommunity repo of packages which recommends using an upstream remote.

It seems overly fragile to require that the remote is called origin. It's not at all unusual for a forked repo to have both an origin remote which represents the fork and an upstream remote for the master/main branch which corresponds to the upstream project. This makes it easy to always checkout the upstream master branch and keep things in sync.