Reusable workflows seem to now require repository visibility = internal

[dkirrane]

Select Topic Area

Question

Body

I have some reusable workflows that were in a private repository.
I was hitting error parsing called workflow ".github/workflows/test.yaml" -> "org/reusable-actions/.github/workflows/reusable-test-workflow.yml@main" : workflow was not found.

When I change org/reusable-actions from private to internal repository visibility it started working again.
I pretty sure private worked before... Have there been changes in this area?

[chrisreddington]

Hey @dkirrane, have you had a chance to look through the Access to reusable workflows section of the Reusable Workflow docs? It sounds like you may need to allow GitHub Actions workflows to access a private repository.

(Be mindful of the warnings/caveats in that second linked doc, particularly around indirect access considerations)

[dkirrane]

Yes in my org/reusable-actions repo I have Accessible from repositories in the 'org' organization.
The caller repo is in same org and it has Allow all actions and reusable workflows set.
Both repos private.

The only thing that worked was changing org/reusable-actions repo from private to internal visibility

[dkirrane]

Also I haven't renamed or moved anything so don't think there is a redirect issue here.

[chrisreddington]

Thanks for following up! I just want to check we're talking about the same settings here, as you mentioned Allow all actions and reusable workflows has been set (I'm assuming this one below):

If so, then that setting is typically used for controlling which reusable workflows/actions can be consumed from within the repo you're configuring. So let's say I'm configuring it on org/my-application, then I'll be able to consume the specified actions and reusable workflows from that repository (you can configure this setting at an organization or enterprise account level, to add restrictions).

However, in this instance, I suspect you may want to take a look at the Actions settings in the org/reusable-actions repository that relate to Allowing access to components in a private repository, a setting that looks like this:

(Bearing in mind the indirect access caveat from the second link in my original post)

If that is configured as expected, then it may be worth raising a support request to dig deeper into your scenario as I am unaware of any recent changes.

[dkirrane]

Yip I have that enabled in the the org/reusable-actions repository.

[chrisreddington]

Thanks @dkirrane. I'd recommend raising a support request to explore the scenario further in that case.

[billy-yuan]

My company is also running into the same issue. When the repository is set as Internal, other repositories can use that repository's Github actions. When I set that same repository to private, other repositories cannot reuse the Github actions.

[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! 💬