Support for using git tags in --start and --end was added in #147. cargo-bisect-rustc translates those to hashes. However, CI commits or only kept for a few months (167 days?). That means you can't go back very far using git tags. I think it would be better if it translated those tags into dates, which go back forever, allowing bisecting of older releases.
If the range is within the last 167 days, cargo-bisect-rustc will automatically switch to CI commits once it has found the specific nightly.
Translating a commit to a nightly date isn't straightforward. However, I think it can use a heuristic of assuming that the commit exists in the nightly of the next day after the commit. That's not always true, but I think should be close enough.
Support for using git tags in
--startand--endwas added in #147. cargo-bisect-rustc translates those to hashes. However, CI commits or only kept for a few months (167 days?). That means you can't go back very far using git tags. I think it would be better if it translated those tags into dates, which go back forever, allowing bisecting of older releases.If the range is within the last 167 days, cargo-bisect-rustc will automatically switch to CI commits once it has found the specific nightly.
Translating a commit to a nightly date isn't straightforward. However, I think it can use a heuristic of assuming that the commit exists in the nightly of the next day after the commit. That's not always true, but I think should be close enough.