a rookie question about GitHub
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
Isn't that the whole point?
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
Yes GitHub keeps previous versions:
Quote:
On GitHub, you can see the commit history of a repository by: Navigating directly to the commits page of a repository. Clicking on a file, then clicking History, to get to the commit history for a specific file.
See: About commits - GitHub Docs[^]
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
Southmountain wrote:
does GitHub still keep all previous versions of my projects?
It sure does. It's a version control system after all.
Southmountain wrote:
then I commit the same version to GitHub website.
Technically, you don't commit to GitHub; you just push your changes to GitHub. With Git you have two complete repositories with all your code history, one on your desktop and another on GitHub. When you commit on your desktop the two repositories are out of sync, but then you push the changes to bring them back in sync.
Mircea
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
It will have all the versions. I suggest getting more familiar with how Git works. Once you commit you also have to push. Maybe a client like Sourcetree would be useful for you. [Learn Git - Tutorials, Workflows and Commands | Atlassian](https://www.atlassian.com/git)
-
Yes GitHub keeps previous versions:
Quote:
On GitHub, you can see the commit history of a repository by: Navigating directly to the commits page of a repository. Clicking on a file, then clicking History, to get to the commit history for a specific file.
See: About commits - GitHub Docs[^]
thanks, the link is great!:rose:
diligent hands rule....
-
Southmountain wrote:
does GitHub still keep all previous versions of my projects?
It sure does. It's a version control system after all.
Southmountain wrote:
then I commit the same version to GitHub website.
Technically, you don't commit to GitHub; you just push your changes to GitHub. With Git you have two complete repositories with all your code history, one on your desktop and another on GitHub. When you commit on your desktop the two repositories are out of sync, but then you push the changes to bring them back in sync.
Mircea
thanks for the explanation!:rose:
diligent hands rule....
-
It will have all the versions. I suggest getting more familiar with how Git works. Once you commit you also have to push. Maybe a client like Sourcetree would be useful for you. [Learn Git - Tutorials, Workflows and Commands | Atlassian](https://www.atlassian.com/git)
thanks for the link! it is very comprehensive!:rose:
diligent hands rule....
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
Southmountain wrote:
then I commit the same version to GitHub website.
Just to follow up on the excellent replies, if you only "commit" your changes to the repo, nothing really happens except that your local version history is updated to reflect the latest change. You have to "push" your changes to GitHub to sync it with your local version changes. So make sure you "push!" :laugh:
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
It can definitely be a little challenging at first. There are some awesome videos and tutorials online that explain it all. The very purpose of Github is to be a "versioning" system, so yes it will indeed retain all versions for you. Learn the command line interface as well. You can do some pretty amazing thing with it. As with anything that is a little complex, if you don't practice and use Github regularly, you will lose familiarity with the process. Good luck!:cool:
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
Southmountain wrote:
TortoiseGit as client...my most recent version only?
You can see the version history via the 'log' in TortoiseGit. At least I believe that is what it is called - if not poke around to find it. Also allows you to diff the versions. You can also see it via the command line but I consider that, for this case, much harder to use.
-
I installed GitHub on my desktop and use TortoiseGit as client. each time I committed my new version to the local folder for this project. then I commit the same version to GitHub website. My question is: does GitHub only have my most recent version only? does GitHub still keep all previous versions of my projects? I used SVN server for long time and heading to GitHub...
diligent hands rule....
You might check out some kind of visual tool for source control. SourceTree is one I know about. It will do/integrate with Git. Being able to visualize it, having buttons to do what (are sometimes) esoteric console commands, and being able to see the result of those button presses reflected in a visual way is probably not the worst thing that could happen for you trying to learn.
-
Southmountain wrote:
does GitHub still keep all previous versions of my projects?
It sure does. It's a version control system after all.
Southmountain wrote:
then I commit the same version to GitHub website.
Technically, you don't commit to GitHub; you just push your changes to GitHub. With Git you have two complete repositories with all your code history, one on your desktop and another on GitHub. When you commit on your desktop the two repositories are out of sync, but then you push the changes to bring them back in sync.
Mircea
-
is it just me or is this MS disease? Rename the same basic function...
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Well, in this case I wouldn't put this diagnostic. If you look at the general philosophy of Git, "commit" and "push" are quite different operations. Commit brings changes under source control while "push" distributes those changes to any number of remote repositories that have been configured. Keep in mind that Git is a distributed version control system so it needed a name for the distribution part.
Mircea
-
Well, in this case I wouldn't put this diagnostic. If you look at the general philosophy of Git, "commit" and "push" are quite different operations. Commit brings changes under source control while "push" distributes those changes to any number of remote repositories that have been configured. Keep in mind that Git is a distributed version control system so it needed a name for the distribution part.
Mircea
Thank you for the clarification. A push now makes sense in the context of team development.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.