There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
Agree with a comment or answer? Like () to up-vote the contribution!
Your first entry on the command line is “cd my quizzes”. Bash tried changing into the directory “my”. Unfortunately there is no such directory, as indicated by the output on the next line.
As branch names must have no whitespaces (aka spaces), this first line should have been “cd my-quizzes” if your branch is called “my-quizzes” as per the exercise.
The directory name in this lesson speciffically is different from what is in the instructions, as can be seen in my screen-shot.
Why that is, I cannot imagine.
If you can’t pass the second check-box, try using the following path for origin:
I found the solution to this. It is completely wrong to what the steps say and the output gives an error but it gives a green check so I can continue. Instead of going to the directory my-quizzes like it wants got to science-quizzes once there input git push origin bio-questions
Apologies for a belated reply, I can see how the instructions might be a little confusing but it makes sense if you follow the previous lessons carefully. An explanation (sadly not a brief one) is below if you wanted to do this correctly.
To start with there is a directory called science-quizzes purportedly written by a colleague, ‘Sally’, and set up as a git repo. You clone this repository to a new directory my-quizzes (back in lesson 2). Note that you have a default remote (tracked repo address for push/pull due to the clone) in your new repo my-quizzes named origin at this point which points back to the original folder due to the clone (described in lesson 3).
In lesson 6 you start working on your own changes after creating a new branch bio-questions (this branch exists only in your my-quizzes repo at this point).
In this specific lesson (7) you move into your own directory my-quizzes which by now has a new branch. You then want to push this new branch to the original repo; the science_quizzes directory. Since the remote already exists under the name origin (due to the clone) you can push with the command: git push <remote> <branch> replacing the remote name and branch to the given ones.
I think there is a small amount of confusion here because the test is probably just checking you enter the exact text expected (of the form git push <remote> <branch>). Passing the lesson might technically require just that but understanding and correctly pushing a branch should be your main goal.
If you then moved to the original repo directory cd ../science-quizzes and check the existing branches (git branch -a for example provides all local/remote branches) you should now find the bio-questions branch available in the original repo (this is the important bit).
A previous comment mentioned the parent directory changes name (curriculum to curriculum-a)-FAQ: Git Teamwork - git push - #6 by mariaburmeister. This does seem to happen (lesson4) for some reason but it shouldn’t affect the workflow as the new repos have the correct remote address anyway (though I’ve no idea why it changes either).
Thanks ever so much - I was having the exact same problem as you guys above - I could not get past question 2. But thanks redcat817 for helping me to resolve this - i followed your suggestions and the check box gave me the green light and I was able to move on.
To /home/ccuser/workspace/curriculum/science-quizzes * [new branch] bio-questions -> bio-questions
Git informs us that the branch bio-questions was pushed up to the remote. Sally can now review your new work and can merge it into the remote’s master branch.
) below.
) to up-vote the contribution!
