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

QtPass, git and windows #173

VictorAtPL opened this Issue Apr 23, 2016 · 5 comments


2 participants

VictorAtPL commented Apr 23, 2016

I cloned repository from remote server to desktop, added profile with certain path and when I try to "Update" it shows me for a second:

bash: pull: No such file or directory

Any thoughts?


This comment has been minimized.


annejan commented Apr 23, 2016

Could it be that your "git executable" is not set in the Setup => Applications ?

Or, wait . . are you using bash on Windows?
That has not been tested at all, can you tell me more about your setup?


This comment has been minimized.

VictorAtPL commented Apr 24, 2016

Alright, so.

  1. on server I created git repo (git init --bare)
  2. on server I created user named git and added ssh key generated on windows
  3. on my windows I cloned git repository (and i tested it out that it works from git bash)
  4. at qtpass i added profile with path which git repository folder is
  5. i switched on use git and tried to "update"
  6. a black console windows appear for a while and show error listed in previous post

Have no idea in which way should I analyze this problem.

Two screenshots:



This comment has been minimized.


annejan commented Apr 24, 2016


I see that you have selected git-bash.exe as the git executable. I might have to make it more clear in the README

Git bash is the interactive Shell you use with bash. QtPass uses the non-interactive scriptable git.exe executable, which is probably in a bin subfolder.

Changing the git executable to git.exe should solve your issue.


This comment has been minimized.


annejan commented Apr 25, 2016

Could you tell me if changing git-bash.exe to git.exe resolved this issue for you @VictorAtPL?


This comment has been minimized.


annejan commented Oct 9, 2016

This has been fixed, is a non-issue and is in the

@annejan annejan closed this Oct 9, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment