I've tried totally uninstalling bors and reinstalling it again, and I also tried re-raising the troublesome PR after that.
Here's a PR where we are experiencing the issue:
Clicking "details" next to the bors check takes us to a page which says: "Page not found".
In the bors log, there are crashes like:
body: "{\"message\":\"Resource not accessible by integration\",\"documentation_url\":\"https://developer.github.com/v3/repos/merging/#perform-a-merge\"}".
It's not clear if this is still to do with workflow permissions. We had, and accepted, a notification of the new permission before I reinstalled bors. Presumably reinstallation would have granted the new permission.
Looking at the apps permissions in our organisation's settings, we see:
I just killed upstream's .github dir and we are away!
It would be nice if bors could be a little more communicative with what is going on. For example it could say "Sorry, I can't do that: there's a change to a github action file .github/workflows/ci.yml".
I also notice that bors doesn't acknowledge "bors try-". It would be nice if it did (didn't it used to say "cancelled"?).
It does not seem to help. I also accepted the new permission on the https://github.com/ddnet/ddnet repository, but bors still hung on a batch containing a pull request that modified a Github actions script.
It would be nice if bors could treat that as a failure for one specific pull request from the batch, retrying other as if the tests failed. Currently, the situation isn't documented well: You only see that bors says that the pull request is "Pending — Waiting in queue" (see e.g. ddnet/ddnet#2188).