For example, after an upgrade of MacOS, xcode cli tools need to be (re)installed. However, before that you can run into an issue with Fork because it will throw a message that directory you're trying to open is not a git repo, offering you to initialize one (sorry no screenshot, forgot to take it as I was battling the issue).
Also, re-scanning the main repo dir always comes up with empty results, although projects/repos are there.
It could be nice to know the reason why something fails in this case, because this sent me in a completely wrong direction while trying to figure out what's wrong.
Only after isolating the issue to Fork (everything else kept working as intended, like IDE etc), I went to check the log and found the offending error π
For example, after an upgrade of MacOS, xcode cli tools need to be (re)installed. However, before that you can run into an issue with Fork because it will throw a message that directory you're trying to open is not a git repo, offering you to initialize one (sorry no screenshot, forgot to take it as I was battling the issue).
Also, re-scanning the main repo dir always comes up with empty results, although projects/repos are there.
I've found this in fork.log:
It could be nice to know the reason why something fails in this case, because this sent me in a completely wrong direction while trying to figure out what's wrong.
Only after isolating the issue to Fork (everything else kept working as intended, like IDE etc), I went to check the log and found the offending error π