Repository navigation
Checks don't run on stubsabot PRs #8434
Description
However, you can trigger them by manually closing and re-opening.
This isn't an ideal state of things. There's a list of possible workarounds here: https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs
Activity
AlexWaygood commentedon Sep 17, 2022
I like the sound of the last option on this list best: creating a minimal GitHub App that would generate tokens for use with GitHub Actions. The only downside I can see is that the app would have to be associated with a maintainer's personal account, so if the maintainer stopped being active for whatever reason, it might be difficult for other maintainers to get access to the app. I think it would still be better than the current state of affairs, however -- if others agree, I'm happy to set up a GitHub App to do this?
AlexWaygood commentedon Sep 17, 2022
Oh, actually, the
sshkey option would maybe be better. I was worried that it wouldn't work so well, because of the fact that it only works withpushevents, rather thanpull_requestevents. But that shouldn't be an issue: stubsabot creates new branches on the typeshed fork, and we can easily adjust thetests.ymlworkflow so that it runs onpushevents for any branches starting withstubsabot/. Thesshoption is used byoddbird/MetaDeployhere, and they seem pretty happy about it (they wrote a nice blog post about their automated PRs for uprading dependencies here.)stubsabot: use an ssh-key when checking out typeshed
stubsabot: use an ssh-key when checking out typeshed (#8844)
srittau commentedon Jul 11, 2026
GitHub recently added a button that allows us to run the tests with one click. Still not ideal (I would prefer to be able to allowlist stubsabot), but I don't think we need a more complicated solution necessarily.