Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub checks not running update_wpt_manifest.yml #1444

Open
KyleJu opened this issue Jun 4, 2021 · 6 comments · Fixed by #4090
Open

GitHub checks not running update_wpt_manifest.yml #1444

KyleJu opened this issue Jun 4, 2021 · 6 comments · Fixed by #4090

Comments

@KyleJu
Copy link
Contributor

KyleJu commented Jun 4, 2021

#1441. After creation, the GitHub checks are stuck and didn't run properly. I have to close and open again to trigger the checks.

It occurs for all the PRs created by https://github.com/web-platform-tests/wpt-metadata/blob/master/.github/workflows/update_wpt_manifest.yml

@KyleJu KyleJu changed the title GitHubs not running update_wpt_manifest.yml GitHub checks not running update_wpt_manifest.yml Jul 7, 2021
@KyleJu
Copy link
Contributor Author

KyleJu commented Jul 10, 2021

Looks like it is a known issue peter-evans/create-pull-request#48

@foolip
Copy link
Member

foolip commented Dec 16, 2021

We can fix this by adding a token as a secret that we use only for creating the PR. Unfortunately, the user behind that token would then be the owner of the PR, instead of github-actions.

@foolip
Copy link
Member

foolip commented Jan 5, 2023

The effect of this is that human intervention is always required to update the manifest. It looks like this might be the cause of #3480.

@past until this is fixed, do you think we can add this to the rotation. Also cc @jcscottiii

@foolip
Copy link
Member

foolip commented Jan 5, 2023

Looks like the issue also affects "Resolve pending metadata" PRs, like #3457.

@jcscottiii
Copy link
Collaborator

jcscottiii commented Jan 5, 2023

There's a new workaround that we should do:

Use a machine account that creates pull requests from its own fork. This is the most secure because the PAT created only grants access to the machine account's fork, not the main repository. This method will trigger on: pull_request workflows to run. Workflows triggered on: push will not run because the push event is in the fork.

All of the affected actions are triggered by on: pull_request so it should work.

@foolip
Copy link
Member

foolip commented Jan 6, 2023

Yeah, that sounds like it would work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants