How to `git bisect` only on one branch's commits?
来源： https://stackoverflow.com/questions/20240526/how-to-git-bisect-only-on-one-branchs-commits
git-bisect
How to `git bisect` only on one branch's commits?
来源： https://stackoverflow.com/questions/20240526/how-to-git-bisect-only-on-one-branchs-commits
How does --no-ff merge break bisect and blame?
问题 Understanding the Git Workflow article says, So you add a new rule: “When you merge in your feature branch, use –no-ff to force a new commit.” This gets the job done, and you move on. Then one day you discover a critical bug in production, and you need to track down when it was introduced. You run bisect but keep landing on checkpoint commits. You give up and investigate by hand. You narrow the bug to a single file. You run blame to see how it changed in the last 48 hours. You know it’s
How do you get git bisect to ignore merged branches?
问题 I'm aware that git bisect is branch-aware by design, so that if between good commit, G, and bad commit, B, you merged in a branch, it needs to take those changes into consideration as well, as the bug may be contained in the branch. In my case I have a dependency as a side branch and I merge in changes to my main project from time to time. The dependency can be considered a library that has a different way of running, different build-system etc. from my main project, but I still want recent
How to use git bisect? [closed]
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . I have read some articles saying that git bisect is awesome. However, I'm not a native speaker and I can't understand why it's awesome. Could someone please demonstrate with some code sample: How to use it? Is it just like svn blame ? 回答1: The idea behind git bisect is to perform a
How can I ignore a directory when doing a Git bisect?
问题 I have a production build directory which often conflicts when merging branches. That's a separate issue. I need to find a problem in the commit history using Git bisect, but I get the following error: Bisecting: a merge base must be tested error: Untracked working tree file 'problem_directory/filename.ext' would be overwritten by merge. Can I ignore problem_directory during the bisect process? 回答1: Build directories should not be checked in for exactly the reason you're encountering.
How does git bisect skip choose the next commit to try?
问题 When using git bisect , one can run git bisect skip to mark the current commit as being an unbuildable / untestable one, to try and get Git to pick some other commit to test instead. How does Git decide which commit to try after a git bisect skip ? Experimenting shows it's not just an adjacent commit, but I can't work out the pattern. Edit : I'm aware the basic git bisect is a binary search, but I'm curious about git bisect skip , which is clearly doing something more complicated.
Git bisect with merged commits
问题 I have a history that looks like this: * 3830e61 Add data escaping. (Bad) * 0f5e148 Improve function for getting page template. * aaf8dc5 Merge branch 'navigation' |\ | * 3e667f8 Add icons. | * 43a07b1 Add menu styles. (Breaks) | * 107ca95 Add Responsive Nav. (Good) * | ea3d736 Add ‘Admin’ notice. * | 17ca0bb Update placeholder text. |/ * f52cc34 Add featured image. * 2abd954 Style placeholders. I am trying to learn more and git bisect , but am having trouble with this history. I know that
Undoing a git bisect mistake
问题 I'm doing a non-automated git bisect via command line. All is going well until I accidentally hit return on the wrong line in my command history, and rather than running the test, I run 'git bisect good' (or bad). Oops - I don't yet know if this commit should be marked good or bad, yet that's what I've done. Can I undo the 'git bisect good' command, or make git forget the result of it, and go back and run the test for that commit? 回答1: Bisect log and bisect replay After having marked
Undoing a git bisect mistake
I'm doing a non-automated git bisect via command line. All is going well until I accidentally hit return on the wrong line in my command history, and rather than running the test, I run 'git bisect good' (or bad). Oops - I don't yet know if this commit should be marked good or bad, yet that's what I've done. Can I undo the 'git bisect good' command, or make git forget the result of it, and go back and run the test for that commit? manojlds Bisect log and bisect replay After having marked revisions as good or bad, issue the following command to show what has been done so far: $ git bisect log