It occurred to me know that we can implement a better heuristic. If a release branch for the next version of Go does not exist yet, gopherbot should not consider creating a backport issue for that version.
Related to #37672.
/cc @toothrot @cagedmantis
It occurred to me know that we can implement a better heuristic. If a release branch for the next version of Go does not exist yet, gopherbot should not consider creating a backport issue for that version.
Related to #37672.
/cc @toothrot @cagedmantis