You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just downloaded mu-repo 1.9.0 on my Windows 10 and I cannot make it see current working dir (I think). Anyway, it seems to not recognize my repos:
> ls
Directory: C:\Users\...\work\repos\private\rust
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 28.01.2021 16:01 coding-challenge
d----- 28.01.2021 16:01 guessing_game
> mu register --all
> mu list
No repository registered. Use mu register repo_name to register repository.
>ls .\coding-challenge\
Directory: C:\Users\...\work\repos\private\rust\coding-challenge
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 20.05.2020 15:01 .devcontainer
d----- 20.05.2020 15:01 .git
d----- 20.05.2020 15:01 src
-a---- 20.05.2020 15:01 8 .gitignore
-a---- 20.05.2020 15:19 148 Cargo.lock
-a---- 20.05.2020 15:01 235 Cargo.toml
-a---- 20.05.2020 15:01 5214 CODE_OF_CONDUCT.md
-a---- 20.05.2020 15:01 1080 LICENSE
-a---- 20.05.2020 15:01 6494 README.md
> mu register .\coding-challenge\
Repository: .\coding-challenge registered
>mu list
Tracked Repositories:
.\coding-challenge
> mu co master
.\coding-challenge does not exist
.\coding-challenge does not exist
> mu register coding-challenge
Repository: coding-challenge registered
> mu list
Tracked Repositories:
.\coding-challenge
coding-challenge
>mu co master
.\coding-challenge does not exist
coding-challenge does not exist
.\coding-challenge does not exist
coding-challenge does not exist
UPDATE:
Apparently all it needed is to add '.mu_repo' file, but I thought it was fixed in 1.4.0
The text was updated successfully, but these errors were encountered:
Hi,
I just downloaded mu-repo 1.9.0 on my Windows 10 and I cannot make it see current working dir (I think). Anyway, it seems to not recognize my repos:
UPDATE:
Apparently all it needed is to add '.mu_repo' file, but I thought it was fixed in 1.4.0
The text was updated successfully, but these errors were encountered: