Skip to content

Commit 6d17957

Browse files
committed
self-hosted-arm64-runners: specify target repo
The create-azure-self-hosted-runners workflow has an input called `runner_repo` which can be used to specify the repository that the runner will be deployed to. It defaults to git-for-windows-automation, which is not the right one in all cases. Let's set the `runner_repo` input to the repository that requested the runner. Ref: https://github.com/git-for-windows/git-for-windows-automation/blob/main/.github/workflows/create-azure-self-hosted-runners.yml#L18C7-L18C18 Signed-off-by: Dennis Ameling <dennis@dennisameling.com>
1 parent c176add commit 6d17957

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

GitForWindowsHelper/self-hosted-arm64-runners.js

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,9 @@ module.exports = async (context, req) => {
4747
'git-for-windows-automation',
4848
'create-azure-self-hosted-runners.yml',
4949
'main', {
50-
runner_scope: 'repo-level'
50+
runner_scope: 'repo-level',
51+
// Repository that the runner will be deployed to. We want to ensure that the runner is deployed to the same repository that triggered the action.
52+
runner_repo: repo
5153
}
5254
)
5355

0 commit comments

Comments
 (0)