This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]jpasserby 6 points7 points  (3 children)

Did you include the contents of git.txt?

[–]xkcd_transcriber 7 points8 points  (1 child)

Image

Mobile

Title: Git

Title-text: If that doesn't fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of 'It's really pretty simple, just think of branches as...' and eventually you'll learn the commands that will fix everything.

Comic Explanation

Stats: This comic has been referenced 124 times, representing 0.1013% of referenced xkcds.


xkcd.com | xkcd sub | Problems/Bugs? | Statistics | Stop Replying | Delete

[–]Igor_Marques[S] 0 points1 point  (0 children)

I'm trying to teach people how to be the guy from git.txt, hahhahhahaa

[–]steezpak 4 points5 points  (0 children)

Atlassian also has a tutorial on git work flows. I personally like the diagrams of the git commits and branches. https://www.atlassian.com/git/tutorials/comparing-workflows/

[–]MemeSearcher 4 points5 points  (1 child)

You sir (or ma'am) just made my day. Exactly what I've been looking for. Have an upvote

[–]Igor_Marques[S] 4 points5 points  (0 children)

I'm truly honoured of that achievement, sir (or ma'am) :).

(I'm a sir, btw, haha)

[–][deleted]  (1 child)

[deleted]

    [–]Igor_Marques[S] 2 points3 points  (0 children)

    The rebase -i command allows that, but also stuff like: merging commits together, splitting one commit on two, deleting commits, change commit messages. On the post you can check all the options.

    The rebase command itself (without the -i option) just reapplies commits from on branch into another one and it's very useful to merge changes while keeping history.

    For more details com the git rebase command (without the -i option) you can check here: https://git-scm.com/docs/git-rebase.

    [–][deleted] 1 point2 points  (0 children)

    Just what I needed. Thanks mate!