detail, and a lot more. This chapter will round out your knowledge of Git so that you are truly a master. Chapter 8 is about configuring your custom Git environment. This includes setting up hook scripts during a Git initiated edit. Your default branch name By default Git will create a branch called master when you create a new repository with git init. From Git version 2.28 onwards, you can set a different after a clone, you should see something like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean This means you have a clean working

detail, and a lot more. This chapter will round out your knowledge of Git so that you are truly a master. Chapter 8 is about configuring your custom Git environment. This includes setting up hook scripts during a Git initiated edit. Your default branch name By default Git will create a branch called master when you create a new repository with git init. From Git version 2.28 onwards, you can set a different after a clone, you should see something like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean This means you have a clean working

detail, and a lot more. This chapter will round out your knowledge of Git so that you are truly a master. Chapter 8 is about configuring your custom Git environment. This includes setting up hook scripts during a Git initiated edit. Your default branch name By default Git will create a branch called master when you create a new repository with git init. From Git version 2.28 onwards, you can set a different after a clone, you should see something like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean This means you have a clean working

status 命令查看哪些文件处于什么状态。 如果在克隆仓库后立即使用此命令，会看到类似这样的 输出： $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean 这说明你现在的工作目录相当干净。换句话说，所有已跟踪文件在上次提交后都未被更改过。 现在，分支名是“master”，这是 默认的分支名。 我们在 Git 分支 中会详细讨论分支和引用。 现在，让我们在项目下创建一个新的 README 文件。 如果之前并不存在这个文件，使用 git status 命令，你 将看到一个新的未跟踪文件： 31 $ echo 'My Project' > README $ git status On branch master Your branch branch is up-to-date with 'origin/master'. Untracked files: (use "git add ..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add"

status 命令查看哪些文件处于什么状态。 如果在克隆仓库后立即 使用此命令，会看到类似这样的输出： $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean 这说明你现在的工作目录相当干净。换句话说，所有已跟踪文件在上次提交后 现在，分 支名是“master”，这是默认的分支名。 我们在 Git 分支 中会详细讨论分支和 引用。 现在，让我们在项目下创建一个新的 README 文件。 如果之前并不存在这个文 件，使用 git status 命令，你将看到一个新的未跟踪文件： $ echo 'My Project' > README $ git status On branch master Your branch branch is up-to-date with 'origin/master'. Untracked files: (use "git add ..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add"

push.default simple #设置推送模式 nothing 直接push会出错，需要显式的指出推送的远程分支，例如 git push origin master current 推送时只会推送当前所在的分支到远程同名分支，如果远程分支不 存在相应的同名分支，则创建该分支 upstream 推送当前分支到它的upstream分支上，这个模式只适用于推送到与 有此git仓库的相关信息，初始化后要设置当前工作的用户名等相关信息，否则 使用全局设置 # git status #查看当前工作目录和暂存区的状态 On branch master No commits yet nothing to commit (create/copy files and use "git add" to track) # echo 'print("hello #提交当前工作目录的所有文件到暂存区（add为暂存操 作），命令最后有一个点. # git status #再次查看状态 On branch master No commits yet Changes to be commi�ed: (use "git rm --cached ..." to unstage) new

"forks_count": 1, 46. "watchers_count": 1, 47. "open_issues_count": 7, 48. "default_branch": "master", 49. "created_at": "2017-02-26T04:29:06-05:00", 50. "updated_at": "2017-03-13T13:51:58-04:00"