Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Development Tools Introduction to Git GitHub and Other Remote Repositories Pulling Changes

Posted by Carlo Hogeveen
Carlo Hogeveen
10,584 Points

"git remote" gives useless "origin"

In reference to the "Pulling Changes" video in the "Introduction to Git" course. The context is a "myclone" repo, that was cloned from a "medals" repo. In this lesson we "learned", that "git remote" tells us that "myclone" was cloned from "origin", and we can pull changes with "git pull [origin]". The obvious question is, is there a way to find out the truth, that the "myclose" repo was cloned from the "medals" repo, and that it has the "medals" repo as remote repo?

2 Answers

Seth Kroger
Seth Kroger
56,413 Points
Seth Kroger
Seth Kroger
56,413 Points

The verbose flag, -v or --verbose, will give you more detail and list where the remotes are pointing to.

Carlo Hogeveen
Carlo Hogeveen
10,584 Points
Carlo Hogeveen
Carlo Hogeveen
10,584 Points

That was the missing info. Thanks!