Automerge can't find recently created PR about enable-pull-request-automerge HOT 2 CLOSED

@peter-evans Thanks for the response, We are seeing it quite frequently, we are using a different token, the create PR is using the temporary token while the automerge requires the PAT. So that does seem to make sense with what you've said.

I think adding the few second delay as you've suggested is best approach for my usecase thanks!

from enable-pull-request-automerge.

Hi @JMoserCricut

As you mentioned, perhaps GitHub's infrastructure doesn't update fast enough sometimes. I would imagine that to be quite a rare occurrence though. Is this happening a lot?

I guess the simplest workaround is to wait some time in between creating the PR and enabling automerge.

- run: sleep 5s

One other thing to check. Are you using the same token to create the PR and enable automerge? If using the same token (and hence the same user) I believe that GitHub's infra caches recently created resources. If you use a different token/user then there might be a delay before the second user can "see" the created resources. That's just my experience using the API, I don't actually know the internals of GitHub.

from enable-pull-request-automerge.