Skip to content
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

I can't push #28

Open
Immortal-Sty opened this issue Feb 26, 2023 · 7 comments
Open

I can't push #28

Immortal-Sty opened this issue Feb 26, 2023 · 7 comments

Comments

@Immortal-Sty
Copy link

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
Copy link
Author

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

Of course.

@Lorssi
Copy link

Lorssi commented Apr 29, 2023

me too

@Lorssi
Copy link

Lorssi commented Apr 29, 2023

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?

@Immortal-Sty
Copy link
Author

@Lorssi

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

@TwIStOy
Copy link

TwIStOy commented Jun 16, 2023

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

@k2s
Copy link
Contributor

k2s commented Aug 9, 2023

this is addressed in #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

@AxelRHD
Copy link

AxelRHD commented Nov 23, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@k2s @TwIStOy @AxelRHD @Lorssi @Immortal-Sty and others