Reusable workflows can't be executed on other GitHub Organizations Self-hosted Runners

[suzuki-shunsuke]

Select Topic Area

Bug

Body

I created a repository to reproduce the issue easily: https://github.com/suzuki-shunsuke/test-hello-reusable-workflow

Issue

Reusable Workflows can't be executed in other GitHub Organizations' Self-hosted Runner.
For example, the Reusable Workflow suzuki-shunsuke/hello-reusable-workflow has an input runs-on to change the worfklow job's runs-on.

on:
  workflow_call:
    inputs:
      runs-on:
        required: false
        type: string
        default: '"ubuntu-latest"'
        description: |
          JSON string for runs-on.
          e.g.
          runs-on: '"macos-latest"'
          runs-on: '["foo"]'
jobs:
  hello:
    runs-on: ${{fromJSON(inputs.runs-on)}}

So callers can change the runs-on:

test-github-hosted-runner:
  uses: suzuki-shunsuke/hello-reusable-workflow/.github/workflows/hello.yaml@4d45c8dba568207710036908955f0608be508320
  with:
    runs-on: >-
      ["macos-latest"]

This works well in case of GitHub hosted runner such as ubuntu-latest, windows-lates, and macos-latest.
But if you specify your Self-hosted Runner labels, the workflow causes the following error.

Called workflows cannot be queued onto self-hosted runners across organizations/enterprises. Failed to queue this job. Labels: '<YOUR SELF HOSTED RUNNER LABELS>'.

What we checked

We checked our GitHub Organization setting and Self-hosted Runner setting, but we can't see any issues.

1. The organization allows all reusable workflows:

Allow all actions and reusable workflows
Any action or reusable workflow can be used, regardless of who authored it or where it is defined.

2. The runner allows All workflows:

Workflow access
Control how these runners are used by restricting them to specific workflows. Learn more about managing runner groups.

3. I can't see any restriction in the side of Reusable Workflow

How to reproduce

A Self-hosted Runner is required.

1. Copy the workflow to your repository
2. Fix runs-on to your Self-hosted Runner labels
3. Run the workflow

Then the workflow job test-github-hosted-runner would pass but test-self-hosted-runner would fail.

Called workflows cannot be queued onto self-hosted runners across organizations/enterprises. Failed to queue this job. Labels: '<YOUR SELF HOSTED RUNNER LABELS>'.

Related issues and discussions

We can find some related issues and discussions, but they are inactive.

• Called workflows cannot be queued onto self-hosted runners across organisations/enterprise actions/runner#1749
• https://github.com/orgs/community/discussions/25214
• https://github.com/orgs/community/discussions/121692

Especially, a GitHub supporter said the issue was solved in the comment, but as some people and me said this issue hasn't been solved yet.
Unfortunately, the discussion was treated as answered, we can't expect the discussion will be handled again.

So I created this discussion.

Workaround

A workaround is to fork Reusable workflows to your GitHub Organizations, but it isn't ideal.

Is the restriction appropriate?

Called workflows cannot be queued onto self-hosted runners across organizations/enterprises. Failed to queue this job. Labels: '<YOUR SELF HOSTED RUNNER LABELS>'.

Apparently, the restriction is intentional.
But I'm not sure if the restriction is appropriate in terms of security.
I'm not sure why we can run third party actions in Self-hosted Runners but can't run Reusable workflows.

Due to this restriction, we can't fully utilize reusable workflows as OSS.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐