Git Guide - Revision history

91.203.168.203: /* Git config example */

2012-05-25T19:13:21Z

‎Git config example

2012-05-25T19:12:58Z

‎Configuring Github

2012-03-06T11:26:49Z

‎Checking if all worked

2011-07-31T15:17:25Z

‎example git config

2011-07-31T15:15:47Z

‎example git config

2011-07-22T14:09:19Z

‎example git config

2011-05-13T10:19:09Z

2011-05-12T15:47:03Z

2011-05-12T15:46:39Z

2011-05-12T15:45:22Z

Grammar corrections

@@ Line 140: / Line 140: @@
 [github]
      user = <Your github username>
 [color]
      diff = auto

@@ Line 106: / Line 106: @@
 [[Image:github_guide-add_ssh_key.jpg  |frame|center|Click on Add another public key]]
 [[Image:github_guide-save_key.jpg |frame|center|Save the key]]
 If you have now added you first github repository you can start working with it.

@@ Line 126: / Line 126: @@
 <pre>
-~ $ ssh git@github.com
+~ $ ssh git@github.com -i ~/.ssh/github-ssh-key
 The authenticity of host 'github.com (207.97.227.239)' can't be established.
 RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
 Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
-Permission denied (publickey).
+PTY allocation request failed on channel 0
 </pre>
 == Needed commands for git ==

@@ Line 140: / Line 140: @@
 <tt>clone</tt>, <tt>pull</tt>, <tt>commit</tt>, <tt>push</tt>
-== example git config ==
+== Git config example ==
-As a nice feature we wto help you set up git so you have a nicer view, for that we edit and/or create two files.
+As a nice feature we want to help you set up git so you have a nicer view, for that we edit and/or create two files.
 First edit/create the the file ~/.gitconfig

← Older revision		Revision as of 15:15, 31 July 2011
Line 176:		Line 176:
	</pre>		</pre>

−	if you ~~know~~ do a commit, you don't need to ~~give a message, it~~ will open your editor set in .gitconfig and show you the .gitmessage.txt where you could replace the first 5 lines with a description. what you did and why, but please never edit the lines after [ticket: X] in the upcomming window. :)	+	If you now do a commit, you don't need to enter the complete base frame everytime on your own. Git will open your editor set in .gitconfig and show you the .gitmessage.txt where you could replace the first 5 lines with a description about what you did and why, but please never edit the lines after [ticket: X] in the upcomming window. :)

← Older revision		Revision as of 14:09, 22 July 2011
Line 141:		Line 141:

	== example git config ==		== example git config ==
		+
		+	As a nice feature we wto help you set up git so you have a nicer view, for that we edit and/or create two files.
		+
		+	First edit/create the the file ~/.gitconfig
		+
		+	<pre>
		+	[user]
		+	name = <Your Name>
		+	email = <Your email for github>
		+	[github]
		+	user = <Your github username>
		+	token = <Your github token>
		+	[color]
		+	diff = auto
		+	status = auto
		+	branch = auto
		+	grep = auto
		+	interactive = auto
		+	showbranch = auto
		+	[core]
		+	editor = <Your prefered editor>
		+	[commit]
		+	template = ~/.gitmessage.txt
		+	</pre>
		+
		+	Then create the following file ~/.gitmessage.txt
		+
		+	<pre>
		+	subject line
		+
		+	config description
		+
		+	[ticket: X]
		+	</pre>
		+
		+	if you know do a commit, you don't need to give a message, it will open your editor set in .gitconfig and show you the .gitmessage.txt where you could replace the first 5 lines with a description. what you did and why, but please never edit the lines after [ticket: X] in the upcomming window. :)

@@ Line 89: / Line 89: @@
 ~ $
 </pre>
 == Configuring Github ==
@@ Line 135: / Line 120: @@
 If you have now added you first github repository you can start working with it.
 == Needed commands for git ==

@@ Line 103: / Line 103: @@
 </pre>
-It will refuse your public key but now you have the added the host to known hosts.
+It will refuse your public key but now you have added the host to known hosts.
 == Configuring Github ==

@@ Line 92: / Line 92: @@
 === Checking if all worked ===
-Now you can check if the all worked. Just run:
+Now you can check if all worked. Just run:
 <pre>