Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

level 5: teamwork * should not be shown #1132

Open
thenameischainbreaker opened this issue Mar 20, 2024 · 2 comments
Open

level 5: teamwork * should not be shown #1132

thenameischainbreaker opened this issue Mar 20, 2024 · 2 comments

Comments

@thenameischainbreaker
Copy link

The level asks to clone a remote repo, but it looks like you start from a local repo already, because main has a *. I was confused for a bit because other levels only the local repo could have a *.

@FaithfulDev
Copy link

I believe the *-sign is indicating what branch you have checked out and not that it's a remote repo. That said, remote repos are usually indicated by a stroked-outline. In fact that is what it appears after you run "git clone". For example, this is how it looks after playing with it:

image

You can see the remote repo at the right side and the checked out branch "foo" with the *-sign.

That said, initially the remove repo has a solid outline and thus would appear as local. I would say that is a bug.

image

This however is just like Remote-Level-1, where you also start out with only a remote repo, just like in Remote-Level-5.

@pcottle
Copy link
Owner

pcottle commented Mar 21, 2024

Thanks @FaithfulDev for explaining here (and on the other issue)!

So in the starting moment on the level, this is actually your local repository that exists, so it shouldn't have the outline. You run git clone to create the remote:
Screenshot 2024-03-21 at 4 52 49 PM

Now there's been some very valid feedback that git clone only really works if a remote repo already exists, so creating a remote repo by running clone doesn't really make sense. I totally agree with that, it just would be really hard to rework all of the lessons with that update.

I'd also say that git clone is the more common command to run before you start interacting with remote repositories, since most people are cloning an existing repo. So it makes sense spiritually why thats the command you run during these lessons

Hope that explains things

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants