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
So at some point I got stuck and copied repos/lab_40 to my working directory as cloned_hello. When I checked what I got I found that I have a remote named origin. However, the command
$ git remote show origin
resulted in a nonexistent absolute path error message (/Users/.../working/git/git_immersion/auto/hello)
I don't know if it is valid or not, but it seems that when editing the .git/config file in the cloned repo:
url = ../hello
git could get rid of that absolute path and that error message.
The text was updated successfully, but these errors were encountered:
gitqlt
changed the title
prepackaged repos refer to nonexisting remote
Prepackaged repos refer to nonexisting remote
May 24, 2020
Hmm, this might be tricky. The repos are built by actually running the commands in the lab programatically. What you're seeing is my build directory because I built labs last :P
I don't think git will set the relative path the way you suggest, unfortunately.
It looks like folks have had success with ~ to access the user's home directory. However, I don't think that will work for us since we don't know where git tutorial will be run from 🤔
Another idea would be to use a "bare repository" which seem to be more for sharing than the repositories in repos -- but I think it would move the ability to just copy the directory.
Open to ideas 😅 Perhaps we could just include a note in the lab to set it manually. Looks like the same problem in lab 50.
So at some point I got stuck and copied
repos/lab_40
to my working directory ascloned_hello
. When I checked what I got I found that I have a remote namedorigin
. However, the commandresulted in a nonexistent absolute path error message (/Users/.../working/git/git_immersion/auto/hello)
I don't know if it is valid or not, but it seems that when editing the
.git/config
file in the cloned repo:git could get rid of that absolute path and that error message.
The text was updated successfully, but these errors were encountered: