Toshikazu Ohashi

@mbarton98 https://github.com/lighttiger2505/sqls/pull/24 > There are a number of reasons for this, but the main problem is that it can be difficult to maintain. Especially with products like Snowflake, BigQuery and...

Thanks. The problem has been reproduced.

This is different from the assumed behavior. I will investigate the possibility of a bug.

I made the same repository as you and tested it. However even if origin was deleted, lab properly referred to the remaining remote. As we are referring to the remote...

No, lab dose not use caching when referring to git remote. Always run git remote command. And if the repository has more than one remote of gitlab, we refer to...

Thanks for the contribution. Your opinion is very informative. I added the ability to virtually define gitlab domain as a solution. You can try this on the following branch. https://github.com/lighttiger2505/lab/pull/77...

Thank you for contributing !!! > Failed collect git remove infos. exit status 128. This error is caused by do `git remote` failing. Please move to the error repository on...

I added code for error tracking of Git command with [this commit](https://github.com/lighttiger2505/lab/commit/60e5079d92928aa696a1dd5d03d0ab04369ede7d). If you install and run this [release binary](https://github.com/lighttiger2505/lab/releases/tag/v0.5.3) you can see more detailed error. Reinstallation can be done...

Please let me check. 1. Running the lab on a windows file system(`/mnt/c`) results in an error. Because git is executed instead of git.exe which should be aliased. 2. Running...

> There should be some way of configuring the git command that is called, maybe an env variable or command line option (something like alias lab='lab --git-cmd=...')? I appreciate your...