x/build/cmd/gopherbot: should not consider backport requests inside backport issues #32533

dmitshur · 2019-06-10T18:11:43Z

A backport issue should never itself be backported, so gopherbot should reject requests to backport inside such issues.

See #32261 (comment) where it happened by accident and caused confusing backport-backport issues to be created.

gopherbot · 2019-07-12T00:53:41Z

Change https://golang.org/cl/185897 mentions this issue: x/build/cmd/gopherbot: do not consider nested backport requests

dmitshur added help wanted Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done. labels Jun 10, 2019

dmitshur added this to the Unreleased milestone Jun 10, 2019

dmitshur mentioned this issue Mar 4, 2020

x/build/cmd/gopherbot: semantically recognize Go<VERSION> in backport messages instead of opening backports for all #34887

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

x/build/cmd/gopherbot: should not consider backport requests inside backport issues #32533

x/build/cmd/gopherbot: should not consider backport requests inside backport issues #32533

dmitshur commented Jun 10, 2019 •

edited

Loading

gopherbot commented Jul 12, 2019

x/build/cmd/gopherbot: should not consider backport requests inside backport issues #32533

x/build/cmd/gopherbot: should not consider backport requests inside backport issues #32533

Comments

dmitshur commented Jun 10, 2019 • edited Loading

gopherbot commented Jul 12, 2019

dmitshur commented Jun 10, 2019 •

edited

Loading