Use Github Actions to track changes in the Helix repository, and automatically open a PR against this repository whenever there is any diff.
If the PR is already opened, then force push to the corresponding branch.
Do nothing if there are no related changes in the Helix. Preferrably, not even cloning Helix.
~Preferrably rely on push based logic, rather than pull based. Instead of scheduling a periodic workflow, it is better to automatically react of changes on Helix side.~ Actually, not that critical.
Use Github Actions to track changes in the Helix repository, and automatically open a PR against this repository whenever there is any diff.
Helix
side.~ Actually, not that critical.Helix
revision into the commit message.