What's needed?
When arm64 runners were introduced, standard runners only worked for public repos, so for private repos one had to create their how custom runners.
This introduced some complexity in the CI workflow:
|
runs-on: ${{ matrix.os }}${{ matrix.arch != 'amd64' && format('-{0}', matrix.arch) || '' }} |
Now GitHub made available the standard arm64 for private repos too.
Proposed solution
Use the new standard arm64 runners always by removing the complicated construction of the runs-on.
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response
What's needed?
When arm64 runners were introduced, standard runners only worked for public repos, so for private repos one had to create their how custom runners.
This introduced some complexity in the CI workflow:
frequenz-repo-config-python/cookiecutter/{{cookiecutter.github_repo_name}}/.github/workflows/ci.yaml
Line 77 in fe49b18
Now GitHub made available the standard arm64 for private repos too.
Proposed solution
Use the new standard arm64 runners always by removing the complicated construction of the
runs-on.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response