Unfortunately, this does not currently trigger the regular PR workflow that would unittest those changes. This is a deliberate limitation of GH actions, as they automatically-generated GITHUB_TOKENs they use do not trigger other workflows themselves.
As a workaround for this, we can simply close and then reopen the PR, which will trigger the usual CI jobs for it, which the PR description says as a reminder. As I don't foresee having to do this very often, I think this workaround is enough and less maintenance than the alternative of creating a GitHub applciation.
Checklist:
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have run linter locally (make lint) and all checks pass.
[ ] I have run tests locally (make test) and all tests pass.
[ ] I have run relevant integration test locally (make integration-xxx for agent related changes)
[ ] I have run relevant e2e test locally (make e2e-xxx for disruptors, kubernetes or cluster related changes)
[ ] Any dependent changes have been merged and published in downstream modules
Description
This PR introduces a CI job that runs
hack/depsyncevery day, and creates (or updates if it exists) a PR with the changes it produces.PR should only be created if the job produces any changes to the git repository.
An example of the PR that would be created can be found here: https://github.com/roobre/xk6-disruptor/pull/28
Unfortunately, this does not currently trigger the regular PR workflow that would unittest those changes. This is a deliberate limitation of GH actions, as they automatically-generated
GITHUB_TOKENs they use do not trigger other workflows themselves.As a workaround for this, we can simply close and then reopen the PR, which will trigger the usual CI jobs for it, which the PR description says as a reminder. As I don't foresee having to do this very often, I think this workaround is enough and less maintenance than the alternative of creating a GitHub applciation.
Checklist:
make lint) and all checks pass.make test) and all tests pass.make integration-xxxforagentrelated changes)make e2e-xxxfordisruptors,kubernetesorclusterrelated changes)