- Bisect is used to mark a commit as good or bad commit
- it is helpful in debugging to identify bad commits
- Fix the issues and as good commits
| To mark commit good with bisect (bisect used for debugging) | git bisect good <commit-id> |
| To mark commit bad with bisect | git bisect bad <commit-id> |
| To list the bisect commits | git bisect log |
| To enter bisect start And mark all commits as good from now | git bisect start git bisect good |
| To enter bisect start And mark all commits as good from now | git bisect start git bisect bad |
| To exit bisect | git bisect reset |
1. Add Single Specific Good bisect commit :
| To mark commit good with bisect (bisect used for debugging) | git bisect good <commit-id> |
2. Add Single Specific Bad bisect commit :
| To mark commit bad with bisect | git bisect bad <commit-id> |
3. Add Multiple commits as Good commits :
| To enter bisect start And mark all commits as good from now | git bisect start git bisect good |
3. Add Multiple commits as Bad commits :
| To enter bisect start And mark all commits as good from now | git bisect start git bisect bad |