Atom 1.18 and Bitbucket


#1

For a personal project, I use Notepad++ and GitExtensions on Windows, with a repository on Bitbucket.

I’m trying to use Atom instead to replace both tools. Everything works very well and even better. Except the final push to Bitbucket. I still have to use GitExtensions for that.

Since Atom 1.18 and the new Git tabs, I can do all the Git actions I need: stage, commit, diff, discard. But when I click the :arrow_up: to push, I have the following error message:

Pageant is running in the background.

What do I need to configure to make it work? I seem to be almost there. Maybe something to change in .git/config?


#2

And if I use HTTPS protocol instead of SSH, I’ve got the following error after typing my password into the Atom prompt:


#3

Could you try pushing from cli and see if you get the same behavior?


#4

Oh well, it doesn’t work any better:

  0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487
AllocationBase 0x0, BaseAddress 0x68570000, RegionSize 0x3B0000, State 0x10000
C:\Program Files (x86)\Git\bin\ssh.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Everything works in CLI, except the push. Same with Atom.

I don’t understand why it works with GitExtensions. It’s configured to use the same Git binary as above. And moreover, I think Atom uses its own Git library (error messages are different)…


#5

The problem lies in the remote config of your repo not Atom. (or github package)
Try this command git remote show origin to validate that the remote is correct.


#6

Forget about the cygwin error message. I had an old Git version. It’s OK in CLI now.

So pushing from Git Bash in GitExtensions:

$ git --version
git version 2.10.1.windows.1

$ git push
Everything up-to-date

And pushing from CLI:

$ git --version
git version 2.10.1.windows.1

$ git push
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Same as Atom. It seems only GitExtensions manage to connect through Pageant.

As for your suggestion, both in CLI and in Git Bash:

$ git remote show origin
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I named my repo bitbucket. Must it absolutely be origin?


#7

For the “empty password” error message over HTTPS, that’s a known bug if your remote URL embeds your username:

You can work around it by adjusting your remote e.g.:

git remote set-url bitbucket https://bitbucket.org/USER/REPO


#8

Thanks, it worked. I have to use the HTTPS URL without the user name and a credential helper.