View source for Guide:Git

Help using '''git'''!

==Basics==
===Commands===
Kinda in usage order?
;<code>git status</code> : Ask git what files need to be sent-off.
;<code>git branch</code> : Ask git to list all the branches, and indicate the one you're working on.
;<code>git add [path]</code> : Tell git to add changed file to be sent off to repo.
;<code>git commit -m "[message]"</code> : Commit all files in staging and add a message describing the changes.
;<code>git push origin [branch]</code> : Send your changed to the git repo., where <code>[branch]</code> is the name of the branch you're working on. Use ''master'' for the main one, otherwise the name is up to you!

===Glossary===
; Branch : ...
; Commit : ...
; Fork : ...
; Merge : ...
; Pull : ...
; Repo / Repository : ...
; Staging : ...

===Setting-up A New Repository===
====Github====
We do this via the {{jargon|CLI|command line}}. So open a terminal, or cmd if you're using Windows. 

# <code>git config user.name [username]</code> to add your username (can be whatever), and
# <code>git config user.email [emailaddress]</code> to add the E-mail address you use to log-in to Github.
# (If you want to add {{jargon|SSH|SSH}} or {{jargon|GPG|GPG}} keys you should generate them now and add them via the web interface).
# Move to the directory where you'll be keeping your project.
# <code>git init</code> to initialise the {{jargon|Repository|repo}}.
# Create a ''readme'' file and a ''.gitignore'' file.
#* Your readme can be plain text or markdown, and should have a little info about the project. You'll have seen a bunch if you've visited Github, they're shown by default when you view a repo's page.
#* The [[#.gitignore|gitignore]] file tells git what you don't and/or do want included in your repository. For example you don't want to make private data like address books and SSH keys public!
# <code>git status</code> will tell you what files you need to send-off to your repo.
# <code>git add .</code> adds everything in your work directory to the queue to go to the repo (called staging). Instead of using a <code>.</code> you can do it for individual files by entering their location.
# <code>git commit -m "[message]"</code> where <code>[message]</code> is a brief description of what you're changing.
# Next you'll need to do some stuff in your browser. Go to Github and create a new empty repository, then find and copy the 'remote repository URL'.<br>(You can do this from the CLI too, but you have to use Github's API and it's kinda clunky)
# <code>git remote add origin [remote repository url]</code> to add the location.
# <code>git push origin master</code> will send off all your changes D:

==Meta Files==
You can add certain dotfiles (filenames that start with a dot, they're a Unixy thing) to tell git to do certain things with your project. The most common is .gitignore, which tells git to ignore certain files and folders in your working directory.

It's a little bit fiddly to make dotfiles on windows, but you can do so in the command prompt. Either:

* <code>NUL> .gitignore</code> to create a new file.
* <code>REN [existing file] .gitignore</code> to rename a file you've already made.

To open a command prompt at your current location in Windows Explorer just type <code>cmd</code> and hit <code>Enter</code> in the location bar. You can jump to the location bar quickly with either <code>F4</code> or <code>Alt+D</code>

===.gitignore===

The '''.gitignore''' file is a list of files and directories that will not be uploaded to [[Distribution:Git|Git]].

They can live multiple places, so you can exlude things globably, or per-project.

====Examples====
* https://git-scm.com/docs/gitignore (docs)
* https://github.com/raysan5/raylib/blob/master/.gitignore

<pre>
# comment
*.ext
file/path/
directory/
[Cc]ase
</pre>

I like to start mine with <code>/*</code> which excludes ''everything'', then tell it exactly what I do want added by prefacing the file and directory names with a <code>!</code>
Ignoring everything first, rather than ignoring everything individually was just the method that involved less typing :) Different methods work better depending on your project and how you set up your directories :)

<pre>
/*
!.gitignore
!.readme.md
!index.html
!styles/
</pre>

===Specific useful things to ignore===
====Unity====
So for [[Unity]] game you probably want to ignore those .pdb files.

* https://gist.github.com/octocat/9257657

<pre>
#	Visual Studio / Unity
*.pdb

#	Temp files
*~
</pre>

===.editorconfig===
I just use the '''.editorconfig''' so when people view the files through Github's web interface the tabs look right, but you can set other stuff like line ending and character encoding in there too. Not sure if these files work with git generally. They are also common in text editors, perhaps the one you're using :)

Example:
<pre>
root = true

[*]
indent_style = tab
indent_size = 4
</pre>

The <code>[*]</code> is specifying which files to apply the arguments too (so you can enter specific extensions with, say:

<pre>[*.{html,md}]</pre>

====See Also====
* [http://editorconfig.org/ editorconfig.org]

==See Also==
* [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.

[[Category:CLI]]