9

I love using git bisect especially for solving regression bugs. However, I realized that it can also be too granular: it points out the exact commit message, what if I simply would like to know in what release did a certain bug happen (by a release I mean a git tag)?

The above need not be mutually exclusive, I can start by finding out the tag that caused the bug, then simply rerun another git bisect on that tag as well.

4

1 回答 1

0

如果您对一组标签有一个总订单，您可以在会话中仅git bisect skip [range]或git bisect skip [range] [range] [range] ...- 每个标签[range]将是tag1..tag2~1, tag2..tag3~1, ... -git bisect

于 2019-12-04T07:47:32.247 回答