Multiple github accounts can't connect about octo.nvim HOT 7 CLOSED

Thanks, it works now. I really appreciate that!

Initially I tried gh.nvim, but it cannot create issues. Thanks again :)

from octo.nvim.

Weird, I thought I replied to this one. My concern was that for correct identification of the aliases, we need to parse the ssh config file which is out of the scope of this plugin. Unless there is a different way Im not familiar with

from octo.nvim.

I’m not sure why, but gh.nvim and lazygit work fine in directories with aliases. Is there no way to define aliases in the lua setup function?

from octo.nvim.

Please try bd6af73 and let me know if it works for you

from octo.nvim.

packer.nvim config:

config = function()
	require("octo").setup({
		ssh_aliases = {
			["github.com-work"] = "github.com",
		},
	})
end,

When issuing :Octo issue create, I receive this error:

Creating issue in work/closing-punchlist. Enter title: test
Do you want to use the content of the current buffer as the body for the new issue?

E5108: Error executing lua Vim:E474: Attempt to decode a blank string
stack traceback:
        [C]: in function 'json_decode'
        ...nvim/site/pack/packer/start/octo.nvim/lua/octo/utils.lua:363: in function 'get_repo_id'
        ...m/site/pack/packer/start/octo.nvim/lua/octo/commands.lua:666: in function 'create_issue'
        ...m/site/pack/packer/start/octo.nvim/lua/octo/commands.lua:23: in function 'a'
        ...m/site/pack/packer/start/octo.nvim/lua/octo/commands.lua:331: in function 'octo'
        [string ":lua"]:1: in main chunk
Press ENTER or type command to continue

also :Octo issue list returns

error connecting to github.com-work
check your internet connection or https://githubstatus.com

gh issue list in that same directory returns issues, however.

from octo.nvim.

Please try again, user config was not being applied

from octo.nvim.

Weird, I thought I replied to this one. My concern was that for correct identification of the aliases, we need to parse the ssh config file which is out of the scope of this plugin. Unless there is a different way Im not familiar with

I replied in #295 sorry, I though it was the same issue

from octo.nvim.