-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check Remote not longer honoured #283
Comments
I think that error actually means it can’t find the git remote (git remote -v). By default it looks for a remote named |
I should've mentioned, if the file does exist in the remote, then it copies
the path. It only fails for new files
…On Mon, 6 Mar 2023, 19:05 Ben Gibson, ***@***.***> wrote:
I think that error actually means it can’t find the git remote (git remote
-v). By default it looks for a remote named origin, but it can be
configured in the settings.
—
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5SMP56FO3WHIU7O7Y5SXTW2YRNBANCNFSM6AAAAAAVRJVZBE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I recently upgraded to 4.3.1, since then check remote is not honoured. I'm using gitlink with a custom git repository and I do not want to check the custom.
For example, I'm writing a pull request and I want to write a Readme referencing a file that is in that same pull request. I want to do this without pushing, since the code is not yet ready.
However, since the last update, even if "Check remote" is unchecked. It will reject to copy the path to my clipboard and a notification will pop up with "Could not find remote for selected file".
Cheers.
The text was updated successfully, but these errors were encountered: