git-commit

问题 Is it possible to modify the commented part of the default git commit message? I want to add a bit more 'context' information for my users. # Please enter the commit message for your changes. # (Comment lines starting with '#' will not be included) # Explicit paths specified without -i nor -o; assuming --only paths... # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # modified: test.txt # 回答1: You can use git hooks for that. Before the person who

问题 I added some files to the index but then by mistake I deleted them with git reset --hard . How do I recover them? Here's what happened: I added all files using git add . I then committed When I checked the status, there were still files that weren't included in the commit from the add, which was strange I added the untracked files again and it worked this time But I wanted everything to be in 1 single commit so I looked up how to unstage what I just committed I used git reset --hard HEAD^ —

问题 There's ways to change the message from later commits: git commit --amend # for the most recent commit git rebase --interactive master~2 # but requires *parent* How can you change the commit message of the very first commit (which has no parent)? 回答1: Assuming that you have a clean working tree, you can do the following. # checkout the root commit git checkout <sha1-of-root> # amend the commit git commit --amend # rebase all the other commits in master onto the amended root git rebase --onto

问题 Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted. I mistakenly added files to Git using the command: git add myfile.txt I have not yet run git commit . Is there a way to undo this, so these files won't be included in the commit? 回答1: You can undo git add before commit with git reset <file> which will remove it from the current index (the "about to

问题 How can I delete a commit on a git remote hosted by github.com? I already found multiple answers on SO that show how to remove a commit from the commit history of a branch. I attempted these, however my commit is still clearly available because I can browser directly to it using its hash. So for clarity, my question is not how to remove a commit from the commit history of all my branches on my remote. My question is how to remove the commit itself, so that there is no record of it on the git

问题 Given at the end is an extracted screenshot from a SourceTree branch tree view (there is a gap in the middle of the screenshot) In that, #1 points to the line which used to be branch 1.7.6.14.X and #2 points to the current status of the same branch. The commit referred to by #3 and the preceding 8 commits on that line were previously attached to branch 1.7.6.14.X . Then another developer supposedly checked out the same branch and did the fix pointed to by #4 . This #4 commit has removed the

问题 I'm currently adding a commit-msg hook that will add the git commit URL as a comment to Jira. The commit URL has the format http://[server]/[group]/[project]/commit/[commit_id] Is it possible to obtain the commit id or is it only produced after the item has been committed? Does this mean I need to implement this in a later hook? 回答1: A git commit id is a SHA-1 hash of: The commit message Author and committer info The date The contents (the hash of the tree) The parent commit hash (or hashes,

问题 I wanted to do source control on my website. There were a lot of files so I just went git add -a Unfortunately, I accidentally committed and pushed a file called credentials.txt that had my ftp and db details. I've tried deleting the file, committing then pushing but it still shows the file when I browse my repo on github in the history. Is there anyway to get rid of this? 回答1: Github has a nice guide on this exact topic. It explains how to get it out of the repository, as well as how to deal

问题 I have two long-running branches dev , and a far future release called future . We create fixes for the supported release by branching from the tag that exhibits the bug, fix it, and then open pull-requests to the two branches. If there is a conflict in the 'future' branch, our developers are suppose to create a new branch, resolve the conflicts, and open another PR to future. Unfortunately, our team is large enough that plenty of these second PRs haven't been made. I need to now figure out

问题 I'm new at git so please bear with me. Say i have a file under version control that includes sensitive data. Sure enough, I put that file in my .gitignore file, so it doesn't get pushed to the repo. The problem now is somewhere in my project i have a line like #include <sensitivedata> or whatever your language of choice is. The problem is whenever somebody clones from that repo, that file is missing and he gets a fatal error when trying to build / compile the solution. So, instead of pushing