-
Notifications
You must be signed in to change notification settings - Fork 1
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
Automate updating of vendored dependencies using Github Action #23
Comments
Are we generally happy using third-party actions? The alternative is to script the pull request creation by hand, which is also possible. Do we mind manually closing and re-opening a PR to trigger any other workflows? The next best alternative is probably to create a GitHub App which trigger the workflows; separate machine account is also possible. Full options listed here. |
Not against them in principle for this repo; but we should select them carefully as have been tripped up in the past by poor implementations.
These days, you can trigger actions manually, too... that's what |
@sebbacon I think Steven's referring to this annoying (but understandable) feature of Github Actions:
So if this repo creates pull requests on itself then by default it won't run any of the tests. Closing and re-opening is a workaround for this. |
We can't check the dependencies easily, because these are vendored. See #23.
This should be possible using something like: https://github.com/marketplace/actions/create-pull-request
We'd want this to run as a scheduled job (once every few hours is probably enough) and also be able to run it manually using
workflow_dispatch
.It would "just" be a case of checking out master, running
./scripts/update-dependencies.sh
and then creating a PR if there are any changes.The text was updated successfully, but these errors were encountered: