Interested to Buy Any Domain ? << Click Here >> for more details...
How can you use git bisect to determine the source of a (regression) bug?
- 1 Answers
- 3 Views
- I also Faced
- E-Mail Answers
Answer / Raghavendra Singh
To find the source of a regression bug using Git Bisect, first mark the current state as 'good' and the last known good commit as 'bad'. Then run the 'git bisect start' command. After that, execute 'git bisect bad' with the path to the latest bad commit. Once Git Bisect has narrowed down the suspect area, it will instruct you to checkout a commit and test whether it's good or bad. Continue this process by either running 'git bisect good' for a good commit or 'git bisect bad' for a bad one, until Git Bisect identifies the commit that introduced the bug.
| Is This Answer Correct ? | 0 Yes | 0 No |
What commands will you use to bring a new feature to the main branch?
What language is used in GIT?
What does ‘hooks’ comprise of in git?
Mention some of the best graphical GIT client for LINUX?
How will you know in git if a branch has already been merged into master?
What are the benefits of using version control system?
What is a git commit and what does the commit object contain?
How can you use git bisect to determine the source of a (regression) bug?
What is ‘head’ in git and how many heads can be created in a repository?
What is the difference between rebasing and merge in git?
What is the function of ‘GIT PUSH’ in GIT?
What is git fork?
VSS 
