Currently, it is difficult to see directly on the GitHub issue tracker whether an open issue
has an active fix available fore review in Gerrit. While gopherbot comments on issues
when a CL mentions them, it doesn't provide visual cues like labels.
I propose to change gopherbot to apply a FixPending label to issues. If the CL is modified (commit message updated), abandoned, or merged, gopherbot should automatically removes the FixPending label.
Plus: if the gopherbot finds the fix cl is merged but the issue is not tracked in the release milestone, it should move the issue to the correct milestone. (I don't fully understand the algorithm, but @dmitshur thinks that's feasible in most cases :-))
If a human operator determines that the CL does not actually solve the issue despite claiming to do so, the recommended action is to amend the CL's commit message.
Currently, it is difficult to see directly on the GitHub issue tracker whether an open issue
has an active fix available fore review in Gerrit. While gopherbot comments on issues
when a CL mentions them, it doesn't provide visual cues like labels.
I propose to change gopherbot to apply a
FixPendinglabel to issues. If the CL is modified (commit message updated), abandoned, or merged, gopherbot should automatically removes the FixPending label.Plus: if the gopherbot finds the fix cl is merged but the issue is not tracked in the release milestone, it should move the issue to the correct milestone. (I don't fully understand the algorithm, but @dmitshur thinks that's feasible in most cases :-))
If a human operator determines that the CL does not actually solve the issue despite claiming to do so, the recommended action is to amend the CL's commit message.