For context, I did a basic "hello world!" git hub tutorial, and felt like I had a handle on it. Then I attempted to do literally anything involving either the command line or gitbash and it just all came crashing down.
Show this thread
I've spent most of my game audio career using Perforce and occasionally SVN for version control, and now I gotta learn git and y'all... I'm way lost. Anyone know any good tutorials? Specifically meant for folks without a computer science background? I am but a humble soundsmith.
-
-
-
Hey everyone, thanks for all the resource links and advice! Y'all are the best. <3
Show this thread
End of conversation
New conversation -
-
-
I’ve been in a similar situation this semester and GitKraken gives it a more useable interface imo.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
- Use a UI for git like TortoiseGit for Windows - Update is basically called pull now - Commit is local to your computer, so you can make lots of little commits with commentary and rewind things even without a connection - "Push" to upload your commits to the server
-
basically my view is git is not fit for human consumption so if you *have* to use git and can't figure out a way out of it, get another computer program to use git for you
End of conversation
New conversation -
-
-
i found source tree + bitbucket to be the most useful & intuitive of the bunch with good UI if you're also using unity, they have a detailed tutorial on that on their blog feed https://unity3d.com/learn/tutorials/topics/cloud-build/creating-your-first-source-control-repository …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Pro Git is my favourite resource. https://git-scm.com/book/en/v2 It's formatted like a book, but I only ever use chapters 2 & 3 to look up things when I need them.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
git is distributed. Each machine stores its own copy of history. One history can have multiple timelines. commit = mark point on a timeline branch = make alternate timeline merge = unite two timelines into one push = send to history to machine pull = receive history from machine
-
there are other common terms used as conventions, but are not actually required to use git: master = the “main” branch origin = the “main” server machine so git push origin master = “send main timeline to the main server”
- Show replies
New conversation -
-
-
I would avoid reading comparisons to other systems learn how Git works from scratch. A few key points: - Git is a database that takes snapshots of filesystems called "commits". It does not store changes, instead it diffs two commits and figures out the changes.
-
- These commits may have any number of "parents" - "branches" are mere files that point to these snapshots - the "stage" (aka "cache") is the snapshot that will be saved if you run "git commit". You modify this stage by using "git add".
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.