Seems like add-menuitem.sh is not available within the dpkg version of the latest preview? :-)

(Sorry for the delay - userecho mails seem to have a delay of quite some days for me..)

WSLg is available since Windows 11 21H2, not the upcoming 22H2. Information on github was just not updated, it seems. No need for hacky workarounds to get smartgit / wslg running on 22H1 / current version. 

We're running smartgit inside WSLg, works just as expected.

There are some (X-Window?) UI bugs regarding window resizing & scrollbars, yet those issues are quite negligible. Performance is great, no trade-offs regarding functionality, we're quite happy with our solution. Keep in mind that rolling updates aren't possible, thus smartgit updates have to be applied manually using dpkg or tar bundle.

1) As we maintain multiple repos, I'd have to either use a more flexible .bat or change .bat with fixed paths for each repo? Setting cd to our parent-folder containing all repos thorws a "not a git repository" error.

2) Even though pulling/pushing/fetching/ls-remote {url} within WSL works fine, when started from smartgit it returns "Could not update branch states (green and red arrows) due to: ls-remote failed (return code 1)". Credential helper is set to cache.

Please don't get me wrong, I'm not criticising smartgit in any way, great product & happily paying customers.  I understand that this issue is not directly linked with smartgit, but the way we, as a WSL-user, use it. Just trying to (help) getting it running w/ wsl seamlessly.

Within WSL, I've set  git config credential.helper 'cache'. forwarder.bat lies within C:\ . Any smartgit option I have to change, rather than git executable? Tried both Smart-git and system owned SSH client.

Thanks for getting back on this issue, Marc!

We're also heavily using WSL2 w/ Smartgit as well as PHPStorm (Jetbrains). Recently shifting to the latter due to this issue, by merging & commiting within PHPStorm, but pushing, stashing and Log-Viewing within Smartgit. Kind of odd, but in the end it works.

As you've already gussed, scenario #4 (Smartgit on Windows, repository within \\wsl$\) would be our case, and we'd greatly appreciate smartgit being able to communicate with WSLs git executable. I've tried both wslgit workarounds and consider them kind of hacky, running into credential helper issues all the time. Would love to see Smartgit work seamlessly together w/ WSL! :)

(Even though, as a dev. myself I do know how annoying this question might be, but is there any chance to get an ETA? :) )