'lg2 pull' does not pull?

[allanolesen]

I have problems pulling the latest commits from upstream, using lg2 pull. It says that all is up-to-date, though lg2 ls-remote origin shows that there are new commits available. Doing an lg2 fetch origin before lg2 pull does not make a difference.

To get the updates to a branch, I need to do this:
lg2 checkout <branch name>
lg2 fetch origin
lg2 merge origin/<branch name>

I think my connection to origin is set up correctly. This is the output of lg2 remote show -v:
origin git@github.com:allanolesen/MyPrivateProject.git (fetch)
origin git@github.com:allanolesen/MyPrivateProject.git (push)

However, I am not so sure that my local branch is set correctly up to track the remote branch. I think this output of lg2 branch --list looks a little strange:
ashellrubbish2 (Checked out, HEAD, local) --> refs/remotes/origin/ashellrubbish2
main (local) --> refs/remotes/origin/main
origin/HEAD (remote)
origin/ashellrubbish2 (remote)
origin/main (remote)

Is it supposed to say 'refs/remotes' in front of the path? I have set the upstream branch with lg2 branch -u origin/ashellrubbish2 while that branch was active.

[kkebo]

I think that your issue is the same as #971. It has been fixed in the TestFlight version, but it has not yet been released to the App Store.

[allanolesen]

Oh. That is definitely the same. Quite embarassing.

In my defense, that issue is closed. I only looked in open issues.

[kkebo]

I'm sorry about that. I'll reopen it and keep it open until the fix is released to the App Store.

[kkebo]

The fix has been released to the App Store. (a-Shell 1.17.4)