This community-built FAQ covers the “generalizations” exercise from the lesson “Git Teamwork”.
Paths and Courses
This exercise can be found in the following Codecademy content:
Web Development
Learn Git
FAQs on the exercise generalizations
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!
Need broader help or resources? Head here.
Looking for motivation to keep learning? Join our wider discussions.
Learn more about how to use this guide.
Found a bug? Report it!
Have a question about your account or billing? Reach out to our customer support team!
None of the above? Find out where to ask other questions here!
Mmmh, this lesson fell a bit short to me.
-
git remote -v lists a Git project’s remotes - does it mean a Git project can have more than one remote? Is there any practical example where that would be the case? How would that work with the git fetch and git merge commands?
- What could be the advantages of working with a team by cloning a project versus each contributor creating a separate branch in the original project directly?
It would have been nice to see this more elaborated in the lesson.
Having multiple remotes is not really common, maybe had it once long ago. Could be useful if you take over a project from another developer and you want to make changes and push these changes to a new (remote) project?
lets say we add another remote to our project:
git remote add another gitlab_url
(where gitlab_url is obvious the url), now if we do git remote -v we should see:
origin github_url (fetch)
origin github_url (push)
another github_url (fetch)
another github_url (push)
so now if we want to fetch we can do: git fetch another master or git fetch origin master
so the third keyword determines which remote is used. Once you fetched the changes you can merge them locally. So nothing to do with remote
If one developer starts the project, makes the initial push, the other developers will have to clone the project. From that point on-wards people work in there own branch (or branch per feature, varies between teams)
2 Likes
Thank you for the quick answer and explanation 
This entire lesson was extremely unclear and needs to be entirely reworked. The instructions often didn’t seem to match what the explanation above was saying, and the projects were even more unclear. Maybe it’s just me.
1 Like
In the lessons, you keep starting them with ‘type cd my-quizzes’, but you will likely already be in that directory from the previous lesson, and this may confuse some people when it gives them an error about file not found.
