Git Hub Question(s)

I could see the value in creating the repo first then cloning it but in my experience I have been told to create the project first get a MVP (minimum viable product) then create a repo and that’s if the lead developer didn’t create the repo for me while I was working on the actual code. So it’s good to know how it works in both cases since you won’t always have a repo to clone first and might not always have access to create the repo.


As you can tell, there are multiple approaches to create a repo.

But I think what would help you more would be to walk through a video of someone going through the process.

There are tons of videos on youtube, but this one seems to be good.

I agree with @Sky020 about using http instead of the SSH key.
For all of my personal projects, I just used the http option.
The only time I used the SSH option was for a project that I didn’t own and we were working with gitlab.

Hope that helps!


If I make a project that doesn’t have a repo at first, I still follow the same steps.

Copy-paste is super effective. You copy-paste the code you have into the local clone of the repo.

It isn’t the only way, but I have far fewer problems with settings when I create the remote repo, clone it locally, then populate it, no matter when the remote repo is created relative to the writing of the initial code.


This worked for me! I don’t know why things were acting so strange earlier. Im going to have to keep doing this regularly to really get it ingrained for sure.

Thanks for your help :pray:

1 Like

A question about commits that isn’t addressed in the video.

Once you modify a file, add and commit it, and then push it up to GitHub it seems to overwrite the old version of that file. I thought it would save the old version. Is there a different step to creating multiple versions of files?

push takes your local version of the repository and makes that the state for the remote version of your repository. If you want to see an older version of the file, you look at the commit history.


This is also why you want to have good commit messages.
If you want to find a previous commit, then it will be easier to find it if the commit message is descriptive.


@JeremyLT @jwilkins.oboe AHhhhh i see now!!!

Wow so glad im making progress on this. Thanks for your help everyone.


YaaY, you go, fren :smiley:

1 Like

Tyty :pray: Im going to start incorporating it into all of my projects now so I can get better at using it.

hey can you elaborate on this a bit? I don’t quite understand what this is that im looking at when I visit the link. There are GitHub challenges?

Some people get really obsessed with this graph
which shows how often they push to GitHub. Personally, I do all of my work on GitHub, so I try to prevent green squares on the weekends and ignore any grey squares during the week because I was probably doing something else important rather than using Git.


Ohhh wow I see :thinking:

So by this you mean saving everything you do on GitHub?

I get paid to write open source software on GitHub, so yea, everything I write is saved on GitHub.


Oh ok that makes sense. Interesting.

Thanks for the help :+1: Its all making sense now.


I am glad that git and github are making more sense now :grinning:

I am also going to link my old post on branches.
You don’t have to worry about branches now.

But later on when you start learning about them, this post might help explain the benefits of using them.

1 Like

Thanks a bunch! Yeah, Im still fuzzy on branches and even pulls. Although Im thinking pulls will be much easier to understand.

Thanks for sharing this. I’ll look through it.

Well, pulls come from merging branches. Basically, it means “pull the history from this branch into this second branch”.

1 Like

Ohh I was under the impression that it was something totally different :sweat_smile: glad I brought it up, thanks.

I used Git Extensions a lot when I first started using Git about five years ago. It’s good because it uses all the proper Git terms but you can see what commands it is using so it also helps you learn the command line. I’m command line only 99% of the time now. Only have to go GUI very occasionally if I’m doing something weird.

1 Like