More Robust Error Handling about gh.nvim HOT 6 CLOSED

Think #63 closes this issue.

It only logs cli interactions, but I think this is where 99.99% of the issues with gh.nvim creep up. Closing for now.

from gh.nvim.

@bradsherman failing to fetch remote branch has typically been:

1. the wrong git protocol (sshs vs https) is being used. The latest commit by @dlvhdr should help fix this.
2. if youre using SSH keys, make sure ssh-agent is running and the keys are properly added to the agent.

Lmk if either of these two help.

from gh.nvim.

Ah, I assumed my gh config was correctly set to ssh. Setting that value correctly fixes the issues. Is there somewhere I can inspect the output of the commands? That would be helpful for debugging issues like this

from gh.nvim.

@bradsherman completely agree, debugging needs an overhaul. I'm working on other larger features at the moment.

I think most of the clues would come from dumping the command arguments and the outputs of the commands from

Sound like something you're willing to take on? In theory, we could add a "debug" flag, which dumps every gh and git cli command that's ran and its output into a text file somewhere? What ya think?

from gh.nvim.

yeah I think I could look into that. My first thought is to doing something like what null-ls does https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main/lua/null-ls/logger.lua. I've flipped the debug flag on to diagnose issues with null-ls in the past

from gh.nvim.

Looks cool. Im down for whatever. My only request is try to build something into litee.nvim or gh.nvim directly.

I have no problems with planetary, but we already require litee.nvim, and i dont want the depedencies to grow even further.

from gh.nvim.