I'm still not using Git or GitHub.

Thanks Sue,. Thanks for a great and encouraging post.

Let me pick your brains even further if I may. Each time you make a commit, it's added to git log, isn't it?

git log 

Unless I'm mistaken, the kind of projects you're talking about have hundreds, if not thousands of commits.

In my ignorance, I can imagine logs growing so extensive, that the compiler, whichever you use, runs out of space and when you want to bring up the log, suddenly you can't find the log and therefore the version of your file that you want. Is this making sense?

If I wanted to find a version of the project that was very early on, almost start from scratch but I've already made hundreds of commits. How else do I keep track of those. Is it a case of keeping a written log of all the committ you think might be important? Am I barking up the wrong tree?

Cheer.s. :0)

Yes its added in the Git Log every commit.

git log

is a favorite command of mine.

I have plenty of Git Repos. Some of them are open source projects and some closed. No matter how tiny the project is I usually use Git. There is just a lot of benefits.

Your log file won't explode on you. That isn't a concern at all! A git log on 30,000 commits takes micro seconds.

There is a few ways to work with history. There is no need to write anything but commits and you may want to use tags. One good way is so start tagging your releases 1.0.0 and 1.1.0.

Also if you type

git log

you will see a commit ID. If you want to go back to that very point in history of the code simply just do this with the proper commit ID:

git checkout ced66ed4e7c2c18873a67eb73b9603dd2bff50fa

Another very helpful commands for understand history I like is:

git log --graph --full-history --all --pretty=format:"%h%x09%d%x20%s"

This will show you pretty colors, merges, and help you visualize it a lot better.

Okay thanks :)

I'm looking forward to having another play with Git tomorrow and I'll let you know how it goes.

Let me know how it goes. Ping back here if you need to. I am happy to help.

2 main questions so far.

I use Windows 7 and the Git Powershell. Once the git log gets too long, I have to cycle through it, bit by bit until I get to "END".

From that moment on, the command line glitches badly. and not even Ctrl C to get out of the log will stop this. I have close and open a new shell to get going again. Is there something I can do to fix?

Secondly the git clone command doesn't seem to be working. Any idea why this might be? :)

One last one for now

Any idea what this error message means. It looks like I followed the right process for getting my git project on the repository at Github.

I feel like I've learned some stuff but still need some work :p

I don't think that is an error. I think it is success?

try

git remote -v

it should give you two lines that look something like this:

origin  git@github.com:githubusername/reponame.git (fetch)
origin  git@github.com:githubusername/reponame.git (push)

if you see that then you are set to push and pull to/from your computer/github

I do get those 2 things, but I need to use

git push origin master

To attempt to put them on github which is when I get the error. It seems to be some sort of missing file.

Edit.

fatal: unable to access 'https://github.com/jg-digital-media/new_repo.git/': err
or setting certificate verify locations:
  CAfile: C:\Users\PC2\AppData\Local\GitHub\PortableGit_c7e0cbde92ba565cb218a521
411d0e854079a28c\mingw32/usr/ssl/certs/ca-bundle.crt
  CApath: none

That is the way I use it. I think git push without any other parameters is being discouraged/depreciated.

The two parameters are important:

origin is the alias for the url (you can see this when you do git remote -v ) , you can rename it to whatever you want, in the below example it is being changed from origin to destination

git remote rename origin destination

https://help.github.com/articles/renaming-a-remote/

Then, master is the branch that you are pushing to: Oftentimes you do not want to push to master. Master should be the 100% functional/production version of your code. This is sort of seems superfluous/silly if you are the only one working on your branch and you are not used to git. But, there is a lot of value into not automatically pushing to master.

For example, let's say you are working with a few people on a project. As different people work on different features and merge them, you probably want to first merge them to a dev branch to make sure that the new merged features work as expected before merging them into master.

So, instead, your collaborators would type git push origin dev to merge into the dev branch instead of master.

Or you may want two people to work on a particular feature, then they would be pushing/pulling from their feature branch before going into master. So they may be typing git pull origin aweseome-new-feature to download the branch they are working on.

Lastly, if you have multiple repositories (i.e. if you deploy to heroku, it will add a repository), you don't always want to push all your changes automatically to all your repositories and in that case you would use the command:

git push heroku master

I googled your error and found this: http://stackoverflow.com/questions/27087483/how-to-resolve-git-pull-fatal-unable-to-access-https-github-com-empty

I have a generated SSH key for github. The set up of my first SSH key was tricky/very hard for me and I had help from more experienced people to set it up the first time. However, I have had to set up other SSH keys since then and it is not really so bad, I just get overwhelmed and doubt myself too much sometimes.

I think as long as you know it's a bit of a pain ahead of time, you can anticipate that and walk through the process of setting up an SSH key and you'll be fine.

Keep going! You've almost got git down!

Yea I'm with you on the getting overwhelmed and doubting myself. But I'll keep trying. I'll start a fresh repo and keep going until I get to grips with it but I'm not getting anywhere with this SSH stuff right now and I'll try another day :)

There's a best answer waiting for somebody though cos I've been helped a fair bit in this thread :)

Hi Jonathan Grieve,

Your first question >>>>> I use Windows 7 and the Git Powershell. Once the git log gets too long, I have to cycle through it, bit by bit until I get to "END". From that moment on, the command line glitches badly. and not even Ctrl C to get out of the log will stop this. I have close and open a new shell to get going again. Is there something I can do to fix?

My thoughts: Slow may be the "windows" itself as I can view logs of over 50,000 commits no problem on a laptop. Control C works in most Unix programs to cancel. When it does not work, the alternative is almost always "q" for quit. Git log will quit with the q key. I do not use Windows so it may be different there. As far as scrolling through faster, you can press the space bar to move down a complete screen, and the w command to move up a full screen. You don't need to go through the whole thing to quit.

Your Second Question >>> Secondly the git clone command doesn't seem to be working. Any idea why this might be? :)

My thoughts: This would never work because you are trying to clone something that does not exists. The git clone is almost always a URL not a word. Here is an old photo I found on GitHub that shows you where to find the URL. https://help.github.com/assets/images/help/gist/gist_clone_btn.png . Here is an example on how to git clone just some random trending project right now I found:

git clone https://github.com/typicode/json-server.git

Also have you ever thought of switching to Linux? :)

The first one is sound, now. Using Q to get out of git log seems to work just fine with no glitching or messiness at all.

To be honest I'm just a Windows kind of guy. :) I think you can get emulators for Mac and Windows but I'm so used to developing on Windows I don't have much time for anything else. Too many bad experiences trying to switch between the platforms.

So if you're accepting a pull request it sounds to me like you'd better know your code and your project inside out and the implications for your project of accepting.

That said, Git is a version control system, so any project owner would have a saved backup of the last good version of the project I suppose :)

One last thing, what is a git project as apposed to another project. Of is if simply a project of any kind served through Git :)

Hi Jonathan,

I guess when they say a 'git project' they mean a repository, so yes.

Good luck

Out of interest, how has the paid account helped you? How much did this cost? Yes, I'll look at this on the Github website later but I thought I'd ask :)

Jonathan Grieve It hasn't yet, because I'm still intimidated by GitHub. Which is why I decided to pay the seven dollars so I could have a private repository where I can play around and mess up stuff absolutely as much as I want to (or more accurately, need to). :) Again, I just got it last night and have spent all day trying to wrap my head around Angular.js and avoiding github like the plague :)

I agree completely. This is most of programming in general. You can't be afraid to break sh*t. Thats how you learn.

Hmmm Using Q seems to have worked, for now. Thanks. One problem solved. :-)

Would we be using a public Repo? Would you have the patience for a complete newbie with a very slow brain? Would we all be able to chip in at any time?

This could be good practice so if all that is cool I'd like to join in :)

Hi Karolin,

I am definitely up for collaborating on this. I am also a newbie to Github, but have used Git for private projects.

Great idea by the way. Treehouse should really look at doing something like this so people can learn to use Github properly

Keep up the good work :D

Karolin Rafalski I'm up for this! :) I know I need to learn git, and have taken the classes here, but I haven't really gotten my hands dirty with it in any practical way. This might be amazing! :)

Awesome, I will be collaborating on this as soon as I get a free minute :D

Thanks Karolin!

Apologies in advance if I break it lol