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

Ruby Build a Simple Ruby on Rails Application Frontend Development Cloning the Project

Eric Posen
Eric Posen
406 Points

This part will throw off people

It's confusing because what you clone from this repository is MUCH further along than where we are in this project. It's not where it is in the video. Also, it's not noted well enough that we should only clone this to learn how, but go back to the version we were already working on.

I disagree as in prior videos you should have pushed to your own repo so in the cloning video you should really clone your own repo.

Eric Posen
Eric Posen
406 Points

Well disagree as much as you want, it confused me. It doesn't say to clone your own repo. The steps to take are to clone his repo.

Eric Posen
Eric Posen
406 Points

EDIT: It appears Adam just deleted his previous comment, so I'm reposting it below for reference:

Adam Sackfield @adamsackfield 8:43PM on April 5, 2014 I was being polite. You are wrong.

--

Unbelievable attitude. This makes me want to cancel my Treehouse account. I was expecting a friendly and welcoming community. I gave honest feedback. It confused me, so it's possible it can confuse other people. It tells you to take the steps to clone their repository. This is pointless since you have pushed your own repo in the steps before, but it's not obvious. Grow up.

As I was saying, you are incorrect on this matter. The previous video Jason pushed up his work to GitHub so that Jim who is working on the project with him can clone it and work on it too. The reason you are seeing more code is because you are cloning their project, as you will see in future videos they will each push and pull copies of it down as they complete different sections to collaborate. Hence the project you cloned being completed.

For these videos as you are working alone you do not need to do the cloning, just the pushing to GitHub to learn how to manage the project.

I was being polite and giving the chance to investigate what I suggested to you and solve the issue yourself as the role of a web developer is to solve problems. You completely dis-regarded what I said. I know the video is not confusing as I have been through them myself. I implore you try going back to the video where the repo is created and you should be able to see that it something you are meant to follow along with.

Eric Posen
Eric Posen
406 Points

To say I am incorrect on pointing out I was confused is ridiculous. Yes, I know it's incorrect to actually clone the project. I am saying the lesson was confusing. Just because you weren't confused, doesn't mean others won't be. I got confused, therefore others might as well.

I will happily guide you through your confusion but you did say "The steps to take are to clone his repo." which is incorrect. As I said I don't mind going through the video's and pasting in the times you should listen to to clarify this matter.

I am sorry if my approach has been any less than satisfactory on this occasion and I am more than willing to help you.