[CLOSED] Github

[SHsuperCM]

Sry for such stupid question..

 

Soo.. I know how to mod(ish),

But now I want to start working on a bigger mod..

I got the idea, I know what I want and expect from the mod,

And I'm ready to start working on it..

But, This time I want to use GitHub to save my code safely..

I never used it and from what I understand I cannot make it private?

I dont know where to start or how, How to save/sync and that stuff..

If someone can give me an guide that shows how to set it up and work with it, It'd be lovely!

[NoVaGaming]

Well do you want to be able to upload files to github with a click of a button or go through the upload where you can only upload 100 files at a time(witch is a pain btw) I could show you but it would be hard through The fourms Got skype or anything?

[SHsuperCM]

Well do you want to be able to upload files to github with a click of a button or go through the upload where you can only upload 100 files at a time(witch is a pain btw) I could show you but it would be hard through The fourms Got skype or anything?

Yeah, That's what I meant.. I've seen MrCrayfish's streams and he just clicks something to upload a file he changes...

Altough, I'd like to know where you learned it from, Tutorial? Post?

[NoVaGaming]

Well the thing is its hard to communicate through the fourms if you have skype it would be esier but to get started get a GitHub Account and

download this https://www.sourcetreeapp.com/

[Matryoshika]

I would recommend you use a graphical user interface for Git, to see what you are doing. Git is very powerful, but sometimes hard to understand what you are doing.

As NoVa linked, there is SourceTreeApp, but I also know of GitKraken & SmartGit. Of course, there are several others out there as well. See which you find the best.

 

You can also use GitLab.com to gain your own "private" project, which can be easily exported to GitHub if wanted (can also import projects from GitHub to GitLab).

[sham1]

I disagree with others in this thread. One should  not use any kinds of wrapers around GIT while they don't even understand it. I find the command-line version to be easier to understand as it gives you more feedback instead of obscuring the actual process of using git behind a pretty GUI.

 

I know there is a steep learning curve, but the most basic git commands one needs are not that hard. Anyway, here is a tutorial.

[Draco18s]

Yeah, except that the documentation for git's command line is ass.

It was written by people to say "look at how smart I am, can YOU understand this?"

[SHsuperCM]

*sigh* I've decided to not use gits because now after trying to use all sorts of UIs I find it wierd and uneccesery.....

I think I'm going to to the backups myself and maybe write something to do this easly and with descriptions....

 

git is wierd... *closed*

[sham1]

Yeah, except that the documentation for git's command line is ass.

It was written by people to say "look at how smart I am, can YOU understand this?"

 

But when one starts with git all they really need is "commit", "push", "pull", "checkout", and "add". And using those is easy.

 

@OP, please don't give up. While git may look daunting, getting to know it is so worth it. Also, if you want to close a thread, lock it.

[SHsuperCM]

@OP, please don't give up. While git may look daunting, getting to know it is so worth it. Also, if you want to close a thread, lock it.

It really isnt for what you have to do for it....

Really I dont find a use for it.. i wanted backup which there are simpler stuff that do that....

 

*Locked*