Question Regarding Runner Limit Per Repository in GitHub Actions Runner Controller

[Nasr-Ladib]

Hello,

I'm currently utilizing your GitHub Actions Runner Controller in a setup where we manage and scale our runners between 2 and 10 instances. We are facing a challenge in resource allocation between repositories, and I'm hoping you could provide some insight or suggestions.

The issue arises when we have certain repositories that require a high number of concurrent jobs, at times reaching up to 30 concurrent jobs. This results in all available runners (given our upper limit of 10) being occupied by a single repository, leaving no runners for other repositories.

In an effort to distribute resources more evenly, I'm looking to impose a limit such that a single repository can only use a maximum of 5 runners concurrently.

I understand that GitHub may not offer an inbuilt feature to limit the number of runners per repository. We're considering creating a custom solution using the GitHub API to enforce this limitation, but that could be a complex process.

Could you provide any recommendations or point me towards any features or methods that could help in achieving this runner limitation per repository?

Your assistance and guidance will be greatly appreciated!

Thank you!