Priority change is ignored if given after r+


#1

While several jobs were queued, I tried changing the priority of a queue job (which had been “bors r+”) by giving the “bors p=1” command. However, it looks like bors ignores priority changes while the job is queued. It would be great to have it honor priority changes dynamically.

Also, using “bors r-” then “bors r+” to force bors to honor the priority, it still used priority 0.


#2

You’re right. That was an oversight. Here’s a pull request to fix that.