Description teo tei 2022-10-08 17:14:55 EDT

I observed the bug in MeGit so I reported it to them, but they say the bug belongs to JGit which they are using.

https://github.com/eclipsesource/megit/issues/22

These two configurations are equally valid in `.git/config` for a repository as far as Git is concerned:

A:
```
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[branch "master"]
        remote = git@github.com:xxxxxxx/yyyyyyy.git
        merge = refs/heads/master
```

B:
```
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = git@github.com:xxxxxxx/yyyyyyy.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = origin
        merge = refs/heads/master
```

and they both result in being able to do "git push" and "git pull" from the command line with no errors.

However, JGit doesn't seem to support the first one.

In MeGit I get the following error when trying to pull:

"The current branch is not configured for pull
No value for key remote.git@github.com:xxxxxxx/yyyyyyy.git.url found in configuration"

I'm not sure whether the actual error message comes from JGit directly.