This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| other:devopsmotd [2023/04/14 08:35] – kamaradski | other:devopsmotd [2023/04/17 08:40] (current) – kamaradski | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Or probably more like " | Or probably more like " | ||
| + | |||
| + | ===== 2023-apr-17 ===== | ||
| + | Tip of the Day: **Using Git Bisect to Find the Cause of a Bug** | ||
| + | |||
| + | In the computer programming and DevOps fields, pinpointing the exact commit that introduced a bug can be a time-consuming process. Git bisect can help you find the problematic commit more efficiently: | ||
| + | |||
| + | * **Start bisecting**: | ||
| + | * **Test commits**: Git bisect will automatically checkout a commit halfway between the good and bad commits. Test this commit to see if the bug is present. | ||
| + | * **Mark the commit**: If the bug is present, use `git bisect bad`. If not, use `git bisect good`. Git bisect will then checkout another commit based on your feedback. | ||
| + | * **Repeat**: Continue testing and marking commits until Git bisect identifies the commit that introduced the bug. | ||
| + | |||
| + | By using Git bisect, you can quickly narrow down the problematic commit and address the bug more efficiently. | ||
| + | |||
| + | Keywords: '' | ||
| + | |||
| ===== 2023-apr-14 ===== | ===== 2023-apr-14 ===== | ||