x/build/cmd/gopherbot: doesn't close re-opened backport issues #31094
Labels
Builders
x/build issues (builders, bots, dashboards)
help wanted
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Issue #29270 was filed about gopherbot being too aggressive about closing backport issues. It fought humans (more than one time) who tried to re-open a backport issue. /cc @bradfitz
The fix to that issue was to have gopherbot check for a
gi.HasEvent("reopened")
event and not consider any re-opened backport issues. It worked to resolve that issue, but it doesn't take into account a situation where a backport issue is re-opened (e.g., because the fix is reverted) and then resolved via another future CL.This happened in #30266.
Until this is resolved, the workaround is to manually close a backport issue. This situation happens very infrequently, so this is not a high priority bug.
The text was updated successfully, but these errors were encountered: