How to choose a runner for codespaces prebuild action?

[yanivzoh]

Select Topic Area

Question

Body

I've set up a prebuild configuration for my repository's codespace, which triggers whenever there's a change in the 'main' branch. Currently, the prebuild action consistently runs on the "Standard GitHub-hosted runners" within my organization. I've introduced a more powerful runner with increased CPU and RAM capacity, and I'm interested in having the prebuild action job utilize this specific runner. Could you guide me on how to achieve this?

[arafajs]

To choose a runner for the codespaces prebuild action, you can use the runs-on keyword in your workflow file. For example, the following workflow file will run the prebuild action on the runner with the ID my-custom-runner:

name: My workflow
on:
  push:
    branches:
      - main

jobs:
  prebuild:
    runs-on: my-custom-runner

To find the ID of your custom runner, you can go to the Runners page in your organization's settings.

Once you have updated your workflow file, you can commit and push it to your repository. The next time the prebuild action is triggered, it will run on the specified runner.

[yanivzoh]

Adding the job run logs (might help):

[yanivzoh]

@arafajs any suggestions?

[alexef]

@arafajs I'm also interested in this

[jtszalay]

Still no solution yet

[zisuu]

We also want to use this. Without that, codespaces make no sense since we have internal packages that are only reachable by our self-hosted runners, so we need to have a way to build our codespaces on the self hosted runners!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[zisuu]

Provide More Information: this topic is not outdated, it is still highly relevant to us. But it seems like this is not the case for GitHub??