01219245/repository setup - ประวัติรุ่นแก้ไข

Jittat: /* Getting started */

2015-02-25T09:31:57Z

Getting started

Jittat: /* git clone */

2014-03-05T04:21:56Z

git clone

Jittat: /* git clone */

2014-03-05T04:19:23Z

git clone

Jittat: /* Getting started */

2014-03-05T04:16:10Z

Getting started

Jittat: /* git clone */

2014-03-05T04:13:29Z

git clone

Jittat: /* git pull */

2014-03-05T04:09:34Z

git pull

Jittat: /* Basic work flows */

2014-03-05T04:08:08Z

Basic work flows

Jittat: /* Push/Pull */

2014-03-05T04:07:24Z

Push/Pull

Jittat: /* Push/Pull */

2014-03-05T04:00:05Z

Push/Pull

Jittat: /* Push/Pull */

2014-03-05T03:58:30Z

Push/Pull

@@ แถว 36: / แถว 36: @@
 * If you have no local Git repository (i.e., you start a new project):
-** You should start with our template as if you are starting to work on the tutorial.  Unzip the template. Rename the template directory to your project's name.
+** You should start by creating a new project as if you are starting to work on the tutorial.  (Call '''cocos new''' and clean up as  outlined in [[01219245/cocos2d-js/Sprites#Let.27s_clean_up_HelloWorld_and_start_with_our_empty_game|Tutorial 100]].)
 ** Create a Git repository by calling <tt>git init</tt> in your project directory.
 ** Create <tt>.gitignore</tt> if you need.
-** Add the files from the template.
+** Add the files.
 ** Commit the changes, so that you have something to '''push''' to the remote repository.
 ** Now depending on the services (GitHub or BitBucket), you should add the remote origin.

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:21, 5 มีนาคม 2557
แถว 112:		แถว 112:
	Git clone will create a new directory with the repository. If you do not specify the ''<tt>directory</tt>'' argument, Git will create the directory with the same name as the repository.		Git clone will create a new directory with the repository. If you do not specify the ''<tt>directory</tt>'' argument, Git will create the directory with the same name as the repository.

−	When you are cloning from GitHub or BitBucket repositories, the web pages show clearly the URL to the repository that you can clone. You have to choose the protocol for communicating with the server. The typical choices are '''https''' or '''ssh'''. Using https might be easier in the beginning if you do not want to deal with SSH credentials (or, if you know nothing about it), but using ssh might be nice later on as you might not have to type your password every time you push or pull from the repository.	+	When you are cloning from GitHub or BitBucket repositories, the web pages show clearly the URL to the repository that you can clone. You have to choose the protocol for communicating with the server. The typical choices are '''https''' or '''ssh'''. Using https might be easier in the beginning if you do not want to deal with SSH credentials (or, if you know nothing about it), but using ssh might be nice later on as you might not have to type your password every time you push or pull from the repository. Therefore, I suggest you to start with the https protocol.
		+
		+	Your typical commands should look like (for GitHub)
		+
		+	git clone https://github.com/username/repository-name.git
		+
		+	or (for BitBucket)
		+
		+	git clone https://username@bitbucket.org/username/repository-name.git

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:19, 5 มีนาคม 2557
แถว 112:		แถว 112:
	Git clone will create a new directory with the repository. If you do not specify the ''<tt>directory</tt>'' argument, Git will create the directory with the same name as the repository.		Git clone will create a new directory with the repository. If you do not specify the ''<tt>directory</tt>'' argument, Git will create the directory with the same name as the repository.

−	When you are cloning from GitHub or BitBucket repositories, the web pages show clearly the URL to the repository that you can clone.	+	When you are cloning from GitHub or BitBucket repositories, the web pages show clearly the URL to the repository that you can clone. You have to choose the protocol for communicating with the server. The typical choices are '''https''' or '''ssh'''. Using https might be easier in the beginning if you do not want to deal with SSH credentials (or, if you know nothing about it), but using ssh might be nice later on as you might not have to type your password every time you push or pull from the repository.

@@ แถว 21: / แถว 21: @@
 == Getting started ==
-Pick the hosting service (GitHub or BitBucket) and create a repository for your project.  If you create a private repository in BitBucket, don't forget to add me (jittat@gmail.com) to the project with Read permission.  See figure below, for BitBucket:
+Pick the hosting service (GitHub or BitBucket) and create a repository for your project.
 [[Image:Bitbucket-read.png]]

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:13, 5 มีนาคม 2557
แถว 100:		แถว 100:

	=== git clone ===		=== git clone ===
		+	When you want to start your local development from a remote repository, you '''clone''' the repository.
		+
		+	It can be done by calling
		+
		+	git clone <repository> [<directory>]
		+
		+	in your working directory.
		+
		+	Git clone will create a new directory with the repository. If you do not specify the ''<tt>directory</tt>'' argument, Git will create the directory with the same name as the repository.
		+
		+	When you are cloning from GitHub or BitBucket repositories, the web pages show clearly the URL to the repository that you can clone.

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:09, 5 มีนาคม 2557
แถว 84:		แถว 84:

	When you want to pull the changes in the remote to your local repository, you call <tt>git pull</tt>. In this course, you might not need to do this that often, unless you do your development on many machines.		When you want to pull the changes in the remote to your local repository, you call <tt>git pull</tt>. In this course, you might not need to do this that often, unless you do your development on many machines.
		+
		+	If you want to start another local repository, you should '''clone''' the remote repository once (see next section). Then you call <tt>git pull</tt> when you want to get the changes.

	The syntax for the pull command is roughly the same as the push command. But you have to be careful if you have many branches, Git pull not only gets the changes, but also merges the changes. More precisely, <tt>git pull</tt> runs the <tt>git fetch</tt> command and then <tt>git merge</tt> the changes to your local branch. If you are working on more than one branch, be careful not to fetch and merge a wrong branch into your working branch.		The syntax for the pull command is roughly the same as the push command. But you have to be careful if you have many branches, Git pull not only gets the changes, but also merges the changes. More precisely, <tt>git pull</tt> runs the <tt>git fetch</tt> command and then <tt>git merge</tt> the changes to your local branch. If you are working on more than one branch, be careful not to fetch and merge a wrong branch into your working branch.

@@ แถว 52: / แถว 52: @@
 The work flow for an individual is easy:
 * To get commits from the remote repository to your local repository, you '''pull'''.
 * If you want to start working on the repository on another machine, you '''clone''' the repository.
-=== Push/Pull ===
+=== git push ===
 '''Push:''' When you want to push your local changes to the remote repository, you call <tt>git push</tt>.  The command takes a few arguments:
@@ แถว 81: / แถว 81: @@
 }}
-'''Pull:''' When you want to pull the changes in the remote to your local repository, you call <tt>git pull</tt>.  In this course, you might not need to do this that often, unless you do your development on many machines.
+=== git pull ===
 The syntax for the pull command is roughly the same as the push command.  But you have to be careful if you have many branches, Git pull not only gets the changes, but also merges the changes.  More precisely, <tt>git pull</tt> runs the <tt>git fetch</tt> command and then <tt>git merge</tt> the changes to your local branch.  If you are working on more than one branch, be careful not to fetch and merge a wrong branch into your working branch.
@@ แถว 95: / แถว 97: @@
 to fetch all the changes and merge into your local branch.
-=== Clone ===
+=== git clone ===

@@ แถว 69: / แถว 69: @@
 However, some default value has been set.   If you leave the ''repository'' out, the default is <tt>origin</tt>.  The ''refspec'' can also be automatically determined.  If you have one branch (e.g., the <tt>master</tt> branch), the default is to push your <tt>master</tt> branch to the remote <tt>master</tt> branch.  If you work on a different branch, Git will try to push that branch.
-'''Notes:''' you may see warnings:
+{{กล่องสี|#e0e0e0|
-  warning: push.default is unset; its implicit value is changing in Git 2.0 from 'matching' to 'simple'.
+  warning: push.default is unset; its implicit value is changing in Git 2.0 from 'matching' to 'simple'. [...]
 '''Pull:''' When you want to pull the changes in the remote to your local repository, you call <tt>git pull</tt>.  In this course, you might not need to do this that often, unless you do your development on many machines.