The bugzilla auto assigner should get deactivated when the bug has the flags
and the assignee is
Otherwise, you'll always have to get back to the PR and reassign it to portmgr... takes only a minute, but gets a bit old after the 20st time...
I'll look into it
(In reply to Oleksandr Tymoshenko from comment #2)
Thank you :)
Special cases should be avoided in autoassigner whereever possible
I'd rather describe this in terms of the implicitly stated goal, which appears ostensibly to be "that issues that need exp-runs need not be *manually assigned* to portmgr"
At present the implemented exp-run mechanism is pull-based (not push based), and in particular, already setup such that portmgr is notified when that flag is set (see screenshot).
The only thing that actually needs to be done is to set the flag, which already happens. That the issue may be Assigned to the current maintainer does not get in the way of portmgr self-assigning issues as they go through the exp run request queue
(In reply to Kubilay Kocak from comment #4)
Since I am not familiar with ports or portmgr workflow, I'll let you decide what is actually required. From the implementation point of view, it's not hard to add.
Can you add some issues that were examples of where the AA behaviour wasn't optimal in your opinion to this issues See Also field please
I'm guessing this is also only an issue when the MAINTAINER is also a committer (@freebsd.org), as this is the only time when AA changes Assignee. Is that correct?
(In reply to Kubilay Kocak from comment #6)
Here are three recent examples:
Here's another one:
... can I do anything to help here?
Because this really starts to get on my nerves :)
(In reply to Tobias C. Berner from comment #10)
Sorry for the delay. I deployed possible fix. Please let me know if it works for you.
(In reply to Oleksandr Tymoshenko from comment #11)
Thank you very much!
It seems your change worked, as pr 249060 was not bounced back to me :)