Skip to content

Verify range in bisect tool #2

Description

@jespertheend

Before the bisect starts, it should first ask whether the first and last commits are good or bad. When both are good or both are bad, it should show an error message. When the first commit is bad and the last commit is good, it should continue like normal except it should look for the first known good rather than first known bad commit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions