git-commit

问题 Good Day. I Try to create a new Branch in my Repo. I made this: Git branch events Git Checkout events That worked. So I changed some files and made Git Status Git add --all Git Commit -m "Commit" That worked well but I tried to push it and that didn't work: Git push -u origin events This is the Error: Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 716 bytes | 716.00

问题 There is a repo say ABC/A. I had forked this repo to my own github say ME/A. I was asked to create a branch on ME/A say x (originally there were develop and master). I had to write some code, so I cloned ABC/A and worked on its develop branch. But now when I have to push the code, I cannot push it to ABC/A as i dont have rights to do so. I have to push the code to ME/A. The problem is, I worked on develop branch for ABC/A but I have to push the code to ME/A x branch. Is it possible to push

问题 When I type the git commit command to commit my file, I get this error message: Microsoft Visual Studio: Microsoft: command not found error: there was a problem with the core editor 'Microsoft Visual Studio'. Please supply the message using either -m or -F option. 回答1: Check you git config core.editor value. It might refer to a path with spaces in it, without quotes. Make sure to use simple quotes when registering that editor path: (And double quotes around the all command expression

问题 When I type the git commit command to commit my file, I get this error message: Microsoft Visual Studio: Microsoft: command not found error: there was a problem with the core editor 'Microsoft Visual Studio'. Please supply the message using either -m or -F option. 回答1: Check you git config core.editor value. It might refer to a path with spaces in it, without quotes. Make sure to use simple quotes when registering that editor path: (And double quotes around the all command expression

问题 I was reading about the difference in using a ~ vs ^ operator in git and I came across this question What's the difference between HEAD^ and HEAD~ in Git? The one thing I could not find a good explanation for online after googling is how does git distinguish the first parent of a merge commit from the second one? Is there a rule of thumb? Take this example where a feature branch is merged into the develop branch, creating the merge commit G . develop feature/foo A D | | B E | | C F \ / G <-

问题 I'm trying to better understand the magic behind git-rebase. I was very pleasantly surprised today by the following behavior, which I didn't expect. TLDR: I rebased a shared branch, causing all commit sha1s to change. Despite this, a derived branch was able to accurately identify that its original commits were "aliased" into new commits with different sha1s. The rebase didn't create any mess at all. Details Take a master branch: M1 Branch it off into branch-X, with some additional commits

问题 Imagine that everytime I commit files, before I push them, I'd like to list them to check. How may I do that ? I tried: git ls-tree -r --name-only master git ls-files -stage If I edit a single file, add then commit it. If I try the above codes, it shows me all my files. I want to list ONLY the files that will be pushed on the current commit. 回答1: Git diff to the rescue on this one. You'll use the --name-only flag. To get the contents of the current commit, use this command: #before stage git

问题 I have to fetch all new commits that were a part when a new tag was created on a Git repo. This needs to be done through GitHub API. For example the Git UI says Tagging Tag1 and has a sha associated with it... let's say the sha is : SHA1 Now how do I get all commits which happened or were a part of Tag1 through GitHub API? I want to store all these commits and perform some analysis on them. 回答1: Based on the clarification on your comment: I want to get all commits between this newly created

问题 I have to fetch all new commits that were a part when a new tag was created on a Git repo. This needs to be done through GitHub API. For example the Git UI says Tagging Tag1 and has a sha associated with it... let's say the sha is : SHA1 Now how do I get all commits which happened or were a part of Tag1 through GitHub API? I want to store all these commits and perform some analysis on them. 回答1: Based on the clarification on your comment: I want to get all commits between this newly created

问题 I understand one always needs a message for committing the changes but when and why do I need to also tag a commit? Let's say I made some changes and I commit using git add -A git commit -m "add feature 1" and now git tag -a -m "includes feature 1" v0.1 The question is when does this make sense. 回答1: It would make sense to specify a tag when you release a version of the software you're producing. You could then do: git tag -a v1.0 -m "Release Version 1.0" Like my comment mentioned, you do not