Cyclic workflow, is it possible? #26391
-
Hi,
In case there are updates on the development branch, the automerge action rebases the branch and force-pushes it. In this case, the CI should restart. This workflow used to work flawlessly with Travis CI. I am having difficulties into reimplementing it with GH actions, though. It looks like that upgrades coming from force-pushes on update branches are not considered for CI. In turn, then, the automerge action does not trigger, as it is configured to start when repository checks are complete. What is the right way to configure such workflow with GHA? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I assume you’re using the
To get around that limitation you’ll need to create a PAT (personal access token) with the required permissions and use that instead (via Secrets). |
Beta Was this translation helpful? Give feedback.
-
Thank you! That was exactly the reason! |
Beta Was this translation helpful? Give feedback.
I assume you’re using the
GITHUB_TOKEN
to push the updates created in the cron job? There’s a limitation to that, see Using theGITHUB_TOKEN
in a workflow:To get around that limitation you’ll need to create a PAT (personal access token) with the required permissions and use that instead (via Secrets).