git-checkout | 易学教程

How can I check out a GitHub pull request?

阅读更多关于 How can I check out a GitHub pull request?

I'd like to check out a previously created pull request (created via GitHub web interface). I searched and found different places where a refs/pull or refs/pull/pr But when I add fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to the git config file and do a git fetch What I'm doing wrong? Should GitHub create automatically the pull/xyz stuff, or do I have to configure something? timbo To fetch a remote PR into your local repo, git fetch origin pull/ID/head:BRANCHNAME where ID is the pull request id and BRANCHNAME is the name of the new branch that you want to create. Once you have created

How can I restore only a few lines from a file recorded in a given commit?

阅读更多关于 How can I restore only a few lines from a file recorded in a given commit?

问题 I want to restore a few lines from a file recorded in an older commit. I can see those lines by running git log -p As a last resort, I'm ready to simply copy those lines from the output of that log, but that would hurt my purist's heart and seems rather unprofessional. I do not want to simply run git checkout <file> because that would discard local changes made to <file> since the commit in question. Instead, I would like to merge changes from that commit into <file> in the working tree using

git: checkout files from another branch into current branch (don't switch HEAD to the other branch)

阅读更多关于 git: checkout files from another branch into current branch (don't switch HEAD to the other branch)

问题 I want to load a different version of the files that exist in another branch into my current branch. git help checkout says: DESCRIPTION Updates files in the working tree to match the version in the index or the specified tree. If no paths are given, git checkout will also update HEAD to set the specified branch as the current branch. Is there a way to checkout all those files, but not update HEAD? 回答1: checkout by providing the current path, . : git checkout other-branch-name -- . This

Get back the changes after accidental checkout?

阅读更多关于 Get back the changes after accidental checkout?

The following was the status of my repo. [~/rails_apps/jekyll_apps/nepalonrails (design)⚡] ➔ gst # On branch design # Changed but not updated: # (use "git add/rm <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: _layouts/default.html # deleted: _site/blog/2010/04/07/welcome-to-niraj-blog/index.html # deleted: _site/blog/2010/04/08/the-code-syntax-highlight/index.html # deleted: _site/blog/2010/05/01/showing-demo-to-kalyan/index.html # deleted: _site/config.ru # deleted: _site/index.html # deleted: _site/static

Is there any way to git checkout previous branch?

阅读更多关于 Is there any way to git checkout previous branch?

I sort of want the equivalent of cd - for git. If I am in branch master and I checkout foo , I would love to be able to type something like git checkout - to go back to master , and be able to type it again to return to foo . Does anything like this exist? Would it be hard to implement? Karl Bielefeldt From the release notes for 1.6.2 @{-1} is a way to refer to the last branch you were on. This is accepted not only where an object name is expected, but anywhere a branch name is expected and acts as if you typed the branch name. E.g. git branch --track mybranch @{-1} , git merge @{-1} , and git

Git checkout: updating paths is incompatible with switching branches

阅读更多关于 Git checkout: updating paths is incompatible with switching branches

My problem is related to Fatal Git error when switching branch . I try to fetch a remote branch with the command git checkout -b local-name origin/remote-name but I get this error message: fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'origin/remote-name' which can not be resolved as commit? If I manually create a branch and then pull the remote branch, it works, just as making a new clone and checking the branch out. Why does it not work on the repository I work with? user167628 I believe this occurs when you are trying to checkout a

Is there a difference between “git reset --hard hash” and “git checkout hash”?

阅读更多关于 Is there a difference between “git reset --hard hash” and “git checkout hash”?

问题 While reset and checkout have different usages most of the time, I can't see what difference there is between these two. There probably is one or nobody would have bothered adding a --hard option to do something the basic checkout can do. Maybe there is a difference is the way you will see the history? 回答1: This answer is mostly quoted from my answer to a previous question: git reset in plain english. The two are very different. They result in the same state for your index and work tree, but

Unstage a deleted file in git

阅读更多关于 Unstage a deleted file in git

问题 Usually, to discard changes to a file you would do: git checkout -- <file> What if the change I want to discard is deleting the file? The above line would give an error: error: pathspec '<file>' did not match any file(s) known to git. What command will restore that single file without undoing other changes? bonus point: Also, what if the change I want to discard is adding a file? I would like to know how to unstage that change as well. 回答1: Assuming you're wanting to undo the effects of git

Git, How to reset origin/master to a commit?

阅读更多关于 Git, How to reset origin/master to a commit?

问题 I reset my local master to a commit by this command: git reset --hard e3f1e37 when I enter $ git status command, terminal says: # On branch master # Your branch is behind 'origin/master' by 7 commits, and can be fast-forwarded. # (use "git pull" to update your local branch) # nothing to commit, working directory clean Since I want to reset origin/header as well, I checkout to origin/master: $ git checkout origin/master Note: checking out 'origin/master'. You are in 'detached HEAD' state. You

What do git checkouts really mean?

阅读更多关于 What do git checkouts really mean?

问题 What are checkout s in git? I know once you do checkout to a particular branch, the HEAD points to that branch. But what does it really mean? Does it mean I can then work on that branch? If yes, then, without checking out a branch, I am not able to work on it? Also, what does remote checkout mean? How is it useful? 回答1: As you noted, HEAD is a label noting where you are in the commit tree. It moves with you when you move from one commit to another. git checkout <commit> is the basic mechanism