Result differences between organisation and repo enumeration

[jasonculligan]

Describe the bug
When an org is enumerated, more self hosted runners are found and reported than when the specific repository within the org is enumerated.

To Reproduce
Steps to reproduce the behavior:

1. $ gato-x e -t $your_org_name would find 3 self hosted runners, let say 2 are in $your_repo_name.
2. $ gato-x e -r $your_org_name/$your_repo_name only shows 1 self hosted runner.

Expected behavior
Same results on the repo should appear regardless of whether it was scanned individually or as part of the org.

Screenshots
Sorry - cant!

** Environment (please complete the following information):**

• OS: Linux Mint 22.1
• Python Version: 3.12.3

[AdnaneKhan]

Thanks for the bug report!

In this case were the runners:

• repo level or org level

And was the user performing enum a repo admin/org admin?

I’ll have to look into whether it’s due to difference in the short circuit behavior for repo/org or something else.

GitHub has changed the runlog format quite a bit and the SH runner feature has been somewhat neglected since GH released their actions insights tab (can conclusively ID SH runners on public repos).