This largely fixes the "create a PR in the job-server repository" workflow.
The existing token is currently expired, so the workflow now fails due to that, which is just about the last step of creating a PR.
However, it may be better to do as ehrQL does and actually move this workflow to the repository where the PR is getting created, then check for updates for interactive-templates. The only drawbacks:
PRs are created on a daily schedule, or when a manual run is triggered.
you have to do the close and then open PR task before CI runs
I'm not sure that's such a problem when the number of updates is so infrequent here. It does remove all the hassle of dealing with tokens (as in ebmdatalab/metrics#194).
I'll include these fixes here for reference in any case.
See also #118.
This largely fixes the "create a PR in the job-server repository" workflow.
The existing token is currently expired, so the workflow now fails due to that, which is just about the last step of creating a PR.
However, it may be better to do as ehrQL does and actually move this workflow to the repository where the PR is getting created, then check for updates for interactive-templates. The only drawbacks:
I'm not sure that's such a problem when the number of updates is so infrequent here. It does remove all the hassle of dealing with tokens (as in ebmdatalab/metrics#194).
I'll include these fixes here for reference in any case.