PRs opened by the github-actions bot don't trigger status checks

[jonathan-innis]

Description

Currently, if a PR is opened by the github-actions bot, status checks will just sit in an Expected state forever. We need to look into why this automation is broken.

Workaround

The current workaround is to push a new commit on the branch yourself or to close and re-open the PR to re-trigger the checks.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[aman0408]

Can I work on this issue?

[aman0408]

This behviour is expected as described in the documentation

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch and repository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

[jonathan-innis]

This behviour is expected

Good point. I wonder if there's a different way that we could trigger workflow runs so that we don't have to manually intervene every time one of these PRs is opened.

[aman0408]

@jonathan-innis can we use this workaround?
peter-evans/create-pull-request#48 (comment)

[jonathan-innis]

can we use this workaround

We need to check with our security team before we could take something like this into the project. Generally, long-term static credentials are frowned upon by security teams because they allow persistent access to the project if they are compromised. We might be able to get around the concern here if the scope of the token is only to open pull requests against the repo. I can check back here with the security team and see what they recommend here.

[jonathan-innis]

@aman0408 Checking in here. Are you still planning to work on this one?

[aman0408]

Yes @jonathan-innis . I have been busy since a couple of weeks but I should be able to make some progress in this week