git-commit

问题 Running a git commit leads to the following output: [manu@host] git: git commit -a -m "StreamIt instrumentation" [master 263410f] StreamIt instrumentation 62 files changed, 6117 insertions(+), 5748 deletions(-) rewrite Code/ALCHEMY/streamit-src-2.1.1/src/at/dms/kjc/cluster/ClusterBackend.java (91%) rewrite Code/ALCHEMY/streamit-src-2.1.1/src/at/dms/kjc/cluster/ClusterCodeGenerator.java (95%) rewrite Code/ALCHEMY/streamit-src-2.1.1/src/at/dms/kjc/cluster/code/FlatIRToCluster.java (94%) rewrite

问题 I have performed git commit followed by a git push . How can I revert that change on both local and remote repositories? $ git log commit 364705c23011b0fc6a7ca2d80c86cef4a7c4db7ac8 Author: Michael Silver <Michael Silver@gmail.com> Date: Tue Jun 11 12:24:23 2011 -0700 回答1: git reset --hard HEAD~1 git push -f <remote> <branch> (Example push: git push -f origin bugfix/bug123 ) This will undo the last commit and push the updated history to the remote. You need to pass the -f because you're

问题 In my local repo I have one commit with an incorrect commit message. I've already published the incorrect commit message with git push . Now the remote repo (which is GitHub-hosted) has the incorrect commit message, too. I've already tried git commit --amend , but found that it will not work for me in this situation because I've made additional commits since the incorrect one. How would you fix this situation? 回答1: Easiest solution ( but please read this whole answer before doing this ): git

问题 In my local repo I have one commit with an incorrect commit message. I've already published the incorrect commit message with git push . Now the remote repo (which is GitHub-hosted) has the incorrect commit message, too. I've already tried git commit --amend , but found that it will not work for me in this situation because I've made additional commits since the incorrect one. How would you fix this situation? 回答1: Easiest solution ( but please read this whole answer before doing this ): git

问题 I have spent a long time reading and trying to figure out git commit --amend, but I still do not understand how the # are used in the editmsg. I am worried to edit this without knowing what I am doing because I have read that git commit --amend only does the most recent commit,and once I save and exit , it will be counted as a new commit. I have accidentally committed and pushed (but the push failed) some large files. But I have also written scripts that were supposed to be pushed from the

问题 I am working on a PAAS app. We provide GIT deployment feature where we pull the code from a Git repo in a temp directory and copy the data to working public directory of the server. The problem with this approach is that it doesn't remove the files from working public directly which were removed in Git Repo. I see apps like DeployHQ somehow extract that list from Git Commits. Do I have to parse the Git history for that or are there any opensource tools that extract the list of Deleted

问题 This question already has answers here : Capturing multiple line output into a Bash variable (6 answers) Closed 2 years ago . I have a Git commit, which has a summary, and then some description. So when I see the commit message via git log --format=%B -n 1 <commit> , it looks like this: Commit Summary Line * Commit Description Line 1 * Commit Description Line 2 * Commit Description Line 3 When I try to store this in a Bash variable, however, thus: message=$(git log --format=%B -n 1 <commit>)

问题 In my Git repository, I created three commits in a row: commit1 , commit2 , and commit3 . I then realized I messed up in commit2 and commit3 , and decided to go back to commit1 . To do that, I ran git checkout commit1 Now I am in commit1 . How do I delete commit2 and commit3 ? 回答1: Check your branch out and then reset it Based on your description and under the assumption you were on some branch called mybranch before checking out commit1 ( C1 in my graphs below), you must be in the following

问题 I am new in Git. Is there possible to create commit message step by step during developing? Because I find it very exhausted to review all changes during commit or committing to frequently. Sorry if I am crowding questions in here :) 回答1: Just check changes in as you make them, don't wait until you have a large amount of changes. Not only will this make your commit messages more manageable, but it will help you version control your work better, allow you to track changes more narrowly,

问题 Let's say I have 5 local commits: commit 1 commit 2 commit 3 commit 4 commit 5 At this point when I'm working, I'd like to go back to commit 2. How would I do so? This was so easy using snapshots in previous versions of Xcode. "Discard changes" only goes back to commit 5, right? 回答1: In Xcode 9: Choose Source Control navigator. Select (branch) committed project. Click "Editor->Checkout ...", or click "Editor->Branch->Checkout ..." This works for me, it restores the entire project at once. 回答2