Sergey Golovin

@stchang sorry for not answering (I had some issues). Yes, of course. I'll improve the readme. > Also, I noticed the example page uses vite. Is this the standard way...

I'm not sure how to test it with `ssh -F /dev/null`, But here's debug: ``` 2024-06-26T10:49:49.494984Z INFO jj_cli::cli_util: debug logging enabled 2024-06-26T10:49:49.545369Z DEBUG run_command:cmd_git_fetch{args=FetchArgs { branch: [Glob(Pattern { original: "*",...

I tried to install it from cargo. Looks like it has the same error so it's not because of nix

Got it, thanks! Here the output: ``` OpenSSH_9.6p1, OpenSSL 3.2.1 30 Jan 2024 debug1: Reading configuration data /dev/null debug2: resolving "ssh.dev.azure.com" port 22 debug1: Connecting to ssh.dev.azure.com [191.235.226.19] port 22....

And jj perfectly works with github using same keys

Sorry, but it didn't. It works for github, but doesn't work for azure (looks like I can't reopen the issue)

Yes, that's correct. But it's true only for azure repos, not for github ones

And one more thing. When I tried to clone a repo I got another error: ``` 2024-06-27T13:52:22.063433Z INFO jj_cli::cli_util: debug logging enabled 2024-06-27T13:52:22.064569Z INFO run_command:build_index_segments_at_operation{operation=Operation { id: OperationId("00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000") }}: jj_lib::default_index::store:...

I'm not sure what changed, but looks like it works for me right now