Tips for using Github???

[Mattyp77]

I just made an account on Github because I really need a way to play with the code of a project, change it, add to it, and know that there will always be a good working version to go back to if I break something. And it would be nice to be able to test new bits of code for new features or just the next step of a project and kind of branch it off in whatever direction that's going with a given label (Next level, add animations, implement gui, and so on) all while keeping previous working versions. If I'm not mistaken, this is exactly what github "version control" is and allows you to do right? So ya like I said, I set up an account and I did start messing with it. I created two repositories but gosh I was not expecting it to be so hard to figure out. I see you can also do things with it in a command line interface. Pretty awesome but no idea where to start with that. But Ill probably hold off on that for a bit anyway and get the basic stuff down first.

So the main things that I'm a bit confused or unsure about is... Where do you start your repository? Do you start coding your project first and then create the repository? Should you create the repository in the IDE which I can do in Pycharm. Or in the Github app? Do you upload the files or clone it? Is cloning cloning from the repository to your local hard drive or from your hard drive to the repository? Do you keep the whole original project in the repository and should the repository be a copy of the project? What are the .vml files and other files that it creates? Is there a difference between Git and Github? Is Git the whole service which includes the command line interface and Github just refers to the repository aspect of it? So I'd be very grateful to anyone who can answer these questions for me and guide me in anyway. Tips, tricks, shortcuts, CLI, whatever. Thanks!

 

[Saul H.]

You simply have to select a hyperlink, and assign a name to your repository. If you are programming in HTML5, create an index file.

 

[Sdfgbdfbhdfhfg54yeh]

So the main things that I'm a bit confused or unsure about is... Where do you start your repository? Do you start coding your project first and then create the repository? Should you create the repository in the IDE which I can do in Pycharm. Or in the Github app? Do you upload the files or clone it? Is cloning cloning from the repository to your local hard drive or from your hard drive to the repository? Do you keep the whole original project in the repository and should the repository be a copy of the project? What are the .vml files and other files that it creates? Is there a difference between Git and Github? Is Git the whole service which includes the command line interface and Github just refers to the repository aspect of it? So I'd be very grateful to anyone who can answer these questions for me and guide me in anyway. Tips, tricks, shortcuts, CLI, whatever. Thanks!

Git is a version control system (sim. to SVN... and others).

Github hosts Git repository's. (sim hosts sites are: bitbucket, gitlab, sourceforge, ...) I have a bitbucket account now, as I had my project killed by sourceforge telling me to read the terms, which I dont see how I violating anything, it was just to see how it all worked not serious code. When I joined bitbucket they had some kind of community project to basically do that kind of thing.

The main concept would be: 1) you create a project [and all of your code files], 2) you create a repository, 3) add/change files & commit, 4) find others to collaborate on your project, ...

Git makes a localized repository, which is everything in the .git folder and that can be ignored. Anyone with a copy of that folder can go back to any previous version.

The documentation for Git is here: https://git-scm.com/doc

 

[Mattyp77]

Git is a version control system (sim. to SVN... and others).

Github hosts Git repository's. (sim hosts sites are: bitbucket, gitlab, sourceforge, ...) I have a bitbucket account now, as I had my project killed by sourceforge telling me to read the terms, which I dont see how I violating anything, it was just to see how it all worked not serious code. When I joined bitbucket they had some kind of community project to basically do that kind of thing.

The main concept would be: 1) you create a project [and all of your code files], 2) you create a repository, 3) add/change files & commit, 4) find others to collaborate on your project, ...

Git makes a localized repository, which is everything in the .git folder and that can be ignored. Anyone with a copy of that folder can go back to any previous version.

The documentation for Git is here: https://git-scm.com/doc

Thanks so much for the explanation! I was messing with it quite a bit last night and getting the hang of it a little. Im thinking I may try some others. It just seams like git is the standard go to and is even linked to everything in coding like IDE's