You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
While working I keep many forks. Sometimes I want to link to specific forks depending on a circumstance. Current config file hardcodes a single remote to force usage.
Describe the solution you'd like
I'd like gitlinker to prompt me which fork to open a link on.
Describe alternatives you've considered
There is a config option for remote, but this is used "full-time" and somtimes I want to link to different forks during the same neovim session, and without changing configs.
The text was updated successfully, but these errors were encountered:
Good idea, I will look into the best way to implement it.
This "prompt in case of multiple remotes" should be guarded behind a config option because I think for 90% of people it can be annoying if the default behavior is to always prompt for a remote.
I'm also accepting suggestions regarding what is the best way to have project local configuration for a gitlinker. Is there any other lua plugin that manages that? 🤔
Guard is OKAY, you can also "remember" a choice for the duration of a Vim session so you do not prompt, but then also add a way to "prompt again" during session if you want to change.
I'm not a big fan of project local configurations if they add a file into the repository.
Is your feature request related to a problem? Please describe.
While working I keep many forks. Sometimes I want to link to specific forks depending on a circumstance. Current config file hardcodes a single remote to force usage.
Describe the solution you'd like
I'd like gitlinker to prompt me which fork to open a link on.
Describe alternatives you've considered
There is a config option for remote, but this is used "full-time" and somtimes I want to link to different forks during the same neovim session, and without changing configs.
The text was updated successfully, but these errors were encountered: