The document states: "To use an action defined in a private repository, both the workflow file and the action must be in the same repository. Your workflow cannot use actions defined in other private repositories, even if the other private repository is in the same organization.".
Will this be a definitive limitation? Or it will be removed for example with the new "Internal repository visibility (beta)"?
Would be great to share action within the org.
Thanks in adavance
Thanks for being here and apologies for the delay in response, as of this moment we don't have any information to share, please know however that I've passed on your request to the team and your feedback is correct hands.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
Same with us. We are looking forward for this feature. So at least we need to see a roadmap for this in order to start using actions at organization level.
I would love to have inter-org access to private repos that are used as actions. I just got bit by this while building out an action in a private repo and finally getting it hooked up to use in another private repo within the same Org. It's not that we can't make the action repo public, it's that we don't want to if we don't have to.
Can you elaborate on how you went about referencing intra-org private Actions in other repos within the Organization? I'm working on this now and receiving 404's in the consuming repository.
- Repo: Action-Test (private)
- Repo: Repo-Using-Action (private)
That is exactly the issue we were running into as well. It gave 404's attempting to download the Action, even though the repo was in the same organization but private.
I'll be trying to use a repo local action as a temporary workaround. Everything in the docs right now touts "public". Maybe we'll see some sort of token passing for the `uses` field to enable private actions utlization.
This!!! There is a pretty big need to be able to use actions from private repositories that are on the same organization.
+1 for this. Currently evaluating using github actions for my workplace amongst 160 private repositories. There may be a way around it for us but it seems odd that we don't have this option within the same organization. We have some 100+ repositories, I don't really want to make a repo public just so it can be shared here, nor do I particularly want to duplicate code 100+ times.
This could be a deal breaker yet for using github actions but hopefully there is a way I can achieve what I want which is basically common methods for deploying a repositories code into the cloud. Maybe there's shared code around that I can use somewhere yet.