Revert "Start waiting for processing by default."#878
Conversation
|
Could we add a changelog note mentioning this revert? We mentioned the original change in the log, so I think the revert should be too. |
|
Sure! I've put this under a 1.0.29 release with today's date on. Let me know if this is not the correct way of doing a change note for a hotfix though. |
Oh I've just realized this PR is targeting |
This reverts commit b661ef1.
7a196e8 to
7ec25e0
Compare
|
Ah, okay that makes sense. I was a bit worried that would make it more difficult to do a hotfix because it would pull in other unrelated changes, but it actually looks like there aren't any, so that should work fine. |
Yeah, if the day ever comes that we have to do a hotfix directly on |
|
👍 |
This reverts commit b661ef1.
It looks like this change caused issues with analyses on pull requests from forks. This is due to the complicated nature of the permissions of workflows run on these pull requests. They are able to upload analyses for their own pull requests refs, but are not able to access other Code Scanning APIs such as the one required to get the status of a delivery.
This reverts adding this new functionality until we update the API to make it able to safely determine whether a pull request should be able to get the status of a particular delivery.
This is a hotfix on the v1 branch.
Merge / deployment checklist