laurentsimon

Follow-up. If we're able to do that, the generator may need to have different buildTypes, one for level 3 and one for level 2 (self-hosted). Or we even call them...

Great finding, thanks. The API https://docs.github.com/en/rest/actions/workflow-jobs?apiVersion=2022-11-28#get-a-job-for-a-workflow-run--code-samples seems to return the labels, so I think we should be able to list the workflow run's jobs and use the label to identify...

we can always fetch the workflows and parse them ourselves if we want

@ramonpetgrave64 that's an important issue we have not had the time to resolve for a while

the OIDC token we fetch would happen in the context of the generator, not the calling repository, no? Additional notes for implementation. I think we need to be able to...

> It seems like the labels alone are not a good way to detect self-hosted runners. I've done some experimenting and found that you can still target your Jobs for...

the [API](https://docs.github.com/en/rest/actions/workflow-jobs?apiVersion=2022-11-28#get-a-job-for-a-workflow-run--code-samples) contains a `"runner_name": "my runner",`. What does this contain? Could we use this API or a similar one to check if the name is _not_ on of the...

Thanks for the info. In the API doc, I see a response example containing: ```yaml "labels": [ "self-hosted", "foo", "bar" ], ``` Is this not what we need? is it...

I thought it's a _requirement_ for a self-hosted runner to have a label `self-hosted`, otherwise it's never routed to a self-hosted runner? Is that assumption not correct?

See https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow#about-self-hosted-runner-labels `All self-hosted runners have the self-hosted label. Using only this label will select any self-hosted runner. To select runners that meet certain criteria, such as operating system or...