Guide:Git - Revision history

Rjt: Tools section with linsk for downloading single directories fro mgithub

2022-12-16T02:28:13Z

Tools section with linsk for downloading single directories fro mgithub

← Older revision		Revision as of 02:28, 16 December 2022
Line 109:		Line 109:
	====See Also====		====See Also====
	* [http://editorconfig.org/ editorconfig.org]		* [http://editorconfig.org/ editorconfig.org]

			==Tools==

			* [https://download-directory.github.io/ download-directory] and [https://minhaskamal.github.io/DownGit DownGit]<br>Web interfaces for downloading a single directory from a git repo, something Git doesn't support natively. I've found it useful for grabbing [[Guide:Assets#Samples\|packs of audio samples]], for example.

	==See Also==		==See Also==

Rjt: /* See Also */ Git For Misfits link

2022-09-06T15:40:47Z

Rjt: Category:CLI, link, typos

2022-03-03T12:01:11Z

Category:CLI, link, typos

← Older revision		Revision as of 12:01, 3 March 2022
Line 8:		Line 8:
	;<code>git add [path]</code> : Tell git to add changed file to be sent off to repo.		;<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 commit -m "[message]"</code> : Commit all files in staging and add a message describing the changes.
	;<code>git push origin [branch]</code> : ~~Sned~~ your changed to the git repo., where <code>[branch]</code> is the name of the branch ~~your~~'e working on. Use ''master'' for the main one, otherwise the name is up to you!		;<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===		===Glossary===
Line 67:		Line 67:

	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>		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 ~~invloved~~ less typing :) Different methods work better depending on your project and how you set up your directories :)		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>		<pre>
Line 79:		Line 79:
	===Specific useful things to ignore===		===Specific useful things to ignore===
	====Unity====		====Unity====
	So for Unity game you probably want to ignore those .pdb files.		So for [[Unity]] game you probably want to ignore those .pdb files.

	* https://gist.github.com/octocat/9257657		* https://gist.github.com/octocat/9257657
Line 112:		Line 112:
	==See Also==		==See Also==
	* [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.		* [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.

			[[Category:CLI]]

Rjt: jargon links

2021-10-12T14:23:06Z

jargon links

← Older revision		Revision as of 14:23, 12 October 2021
Line 21:		Line 21:
	===Setting-up A New Repository===		===Setting-up A New Repository===
	====Github====		====Github====
	We do this via the ~~[[Glossary:Main_Page#~~CLI\|command line]]. So open a terminal, or cmd if you're using Windows.		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.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.		# <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 ~~[[Glossary:Main_Page#~~SSH\|SSH]] or ~~[[Glossary:Main_Page#~~GPG\|GPG]] keys you should generate them now and add them via the web interface).		# (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.		# Move to the directory where you'll be keeping your project.
	# <code>git init</code> to initialise the ~~[[Glossary:Main_Page#~~Repository\|repo]].		# <code>git init</code> to initialise the {{jargon\|Repository\|repo}}.
	# Create a ''readme'' file and a ''.gitignore'' file.		# 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.		#* 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.

Rjt: /* See Also */ Removed link to Distribution:Git

2021-06-13T21:20:50Z

See Also: Removed link to Distribution:Git

← Older revision		Revision as of 21:20, 13 June 2021
Line 111:		Line 111:

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

Rjt: Working on Basics section-repo set, useful commands. Note on .editorconfig being a Github thing. Added some .gitignore example

2018-04-03T09:39:06Z

Working on Basics section-repo set, useful commands. Note on .editorconfig being a Github thing. Added some .gitignore example

@@ Line 1: / Line 1: @@
-Help using git!
+Help using '''git'''!
 ==Basics==
 ==Meta Files==
@@ Line 29: / Line 64: @@
 directory/
 [Cc]ase
 </pre>
@@ Line 46: / Line 92: @@
 ===.editorconfig===
-I just use the '''.editorconfig''' so when people view the files through the web interface the tabs look right, but you can set other stuff like line ending and character encoding in there too.
+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:

Rjt: /* .editorconfig */ Link to editorconfig.org

2018-04-03T07:29:21Z

.editorconfig: Link to editorconfig.org

← Older revision		Revision as of 07:29, 3 April 2018
Line 60:		Line 60:

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

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

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

Rjt: Info on meta files .gitignore and .editorconfig

2018-04-03T07:24:15Z

Info on meta files .gitignore and .editorconfig

@@ Line 2: / Line 2: @@
 ==Basics==
 ==See Also==
 * [[Distribution:Git]]
 * [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.

Rjt: Created

2018-04-02T18:26:59Z

Created

New page

Help using git!

==Basics==

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

← Older revision		Revision as of 15:40, 6 September 2022
Line 112:		Line 112:
	==See Also==		==See Also==
	* [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.		* [http://ohshitgit.com/ Oh shit, git!] - Cures for tricky git problems.
			* [https://leetusman.com/nosebook/git-for-artists Git For Misfits (and artists)] - Git guide not aimed at programmers.

	[[Category:CLI]]		[[Category:CLI]]