logseq-plugin-git icon indicating copy to clipboard operation
logseq-plugin-git copied to clipboard

I can't push

Open Immortal-Sty opened this issue 2 years ago • 7 comments

What happened

I can't push by this plugin.

Git push failed
fatal: No configured push destination.
Either specify the URL from the command-line or configure a remote repository using

git remote add <name> <url>

and then push using the remote name

git push <name>

But I can push by powershell.

PS C:\Files\Long\Logseq\Note> git push github master
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 399 bytes | 199.00 KiB/s, done.
Total 4 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To github.com:Immortal-Sty/Logseq-note.git
   20b299f..a83f32c  master -> master

It's strange.

My system

  • Computer system: Windows 11 22H2;
  • Logseq version: 0.8.17;

Immortal-Sty avatar Feb 26 '23 03:02 Immortal-Sty

have you add remote repo first by command "git remote add"?

Of course.

Immortal-Sty avatar Mar 06 '23 10:03 Immortal-Sty

me too

Lorssi avatar Apr 29 '23 13:04 Lorssi

What happened

I can't push by this plugin.

Git push failed
fatal: No configured push destination.
Either specify the URL from the command-line or configure a remote repository using

git remote add <name> <url>

and then push using the remote name

git push <name>

But I can push by powershell.

PS C:\Files\Long\Logseq\Note> git push github master
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 399 bytes | 199.00 KiB/s, done.
Total 4 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To github.com:Immortal-Sty/Logseq-note.git
   20b299f..a83f32c  master -> master

It's strange.

My system

  • Computer system: Windows 11 22H2;
  • Logseq version: 0.8.17;

Have you solved it now?Can you tell me how it was resolved?

Lorssi avatar Apr 29 '23 13:04 Lorssi

@Lorssi

No. Actually, I've given up this plugin.

Immortal-Sty avatar Apr 29 '23 14:04 Immortal-Sty

The push action seems to use just git push. Maybe you should set your remote name as origin and branch is master?

TwIStOy avatar Jun 16 '23 02:06 TwIStOy

this is addressed in https://github.com/haydenull/logseq-plugin-git/pull/39

  • it will work with GIT repositories without remote repository configured (it will not fail on push)
  • it will push to remote repository only if you have one and if you set it as upstream for current branch git push --set-upstream origin master
    • if you cloned your repository then all should be fine
    • to add the remote repository do git remote add origin <REMOTE_URL> first

always test git commit, git push and git pull from command line if you have problems

k2s avatar Aug 09 '23 13:08 k2s

I have nearly the sampe problem now.

Since yesterday Ctrl+S worked as expected. But today a commit is created, but the push failes without errors. I can push the new commit manually with the powershell. But that is very unconvenient. How can I track down the error?

Thanks.

AxelRHD avatar Nov 23 '23 10:11 AxelRHD