From 6d17957bfdd11f6a744da25b537c51c1ad139784 Mon Sep 17 00:00:00 2001 From: Dennis Ameling Date: Tue, 30 Apr 2024 22:32:39 +0200 Subject: [PATCH] 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 --- GitForWindowsHelper/self-hosted-arm64-runners.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/GitForWindowsHelper/self-hosted-arm64-runners.js b/GitForWindowsHelper/self-hosted-arm64-runners.js index 1cbc70d..c71b8ef 100644 --- a/GitForWindowsHelper/self-hosted-arm64-runners.js +++ b/GitForWindowsHelper/self-hosted-arm64-runners.js @@ -47,7 +47,9 @@ module.exports = async (context, req) => { 'git-for-windows-automation', 'create-azure-self-hosted-runners.yml', 'main', { - runner_scope: 'repo-level' + runner_scope: 'repo-level', + // 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. + runner_repo: repo } )