Actions in this workflow must be: within a repository owned by #26609
-
I’ve tried changing the Actions settings in one of my repositories, to “Allow local actions only”. However, an action I have on it, which is scheduled to run daily, failed with the error: “actions/checkout@master, actions/setup-python@master, actions/checkout@master, actions/setup-python@master, and docker/login-action@v1 are not allowed to be used in David-Lor/Docker-Python-Git-App. Actions in this workflow must be: within a repository owned by David-Lor” (links to workflow file and failed run). From what I understand reading the description of the setting (“Only actions defined in a repository within David-Lor can be used.”), the action should still be running, since it’s in my own repository. |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 3 replies
-
Only the workflow is defined in your repository. The actions listed in the error messages are owned by the actions and docker organizations. You can see that by the part in front of the first slash, e.g. |
Beta Was this translation helpful? Give feedback.
-
Oh I see! it makes sense. The naming can be confusing sometimes 😅 |
Beta Was this translation helpful? Give feedback.
-
What then is the remedy? If the repository is owned by me, but docker and actions aren't? Does it mean I cannot use checkout, setup, and cache?
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
@mouse07410, the error message shows you're using 3 actions that aren't yours: The repositories they come from belong to the |
Beta Was this translation helpful? Give feedback.
-
Could you please guide me? How can I allow them? What do I need to do? |
Beta Was this translation helpful? Give feedback.
-
Thank you! Much better! From three, now the problem is reduced to one action:
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
That's odd, I do have a "report a bug" option on that page. I wonder if the direct link works for you? 😅 https://support.github.com/contact/bug-report Meanwhile you can use the "allow all actions and reusable workflows" option to disable limits on what you can call with |
Beta Was this translation helpful? Give feedback.
-
Thank you - opened ticket https://support.github.com/ticket/personal/0/2077502 In the meanwhile, as a workaround I had to relax to "Allow all actions and reusable workflows". Not sure what the security consequences are... Also, an unrelated question: it looks like I've exhausted "Actions and Packages Storage" - how do I (a) find out what actions or packages consumed it, and (b) clear it all out? Thanks! |
Beta Was this translation helpful? Give feedback.
-
For a personal repository, probably none at all. That setting simply restricts what you can call with
My first suspicion would be artifacts. Also in the billing section of your settings you can get a usage report, maybe that helps, not sure how detailed it is. |
Beta Was this translation helpful? Give feedback.
-
I think you're correct. It says the space is taken by prebuilt's. Only question - there are four pages of prebuilt in one project only (the one we're talking about). I don't think I have prebuilt in other projects, but did not check them all. What would be a good way to delete all of the old prebuilt's? There's no way provided in the billing section, and I saw no way on the repo page. After I've deleted several prebuilt's manually, there was no increase of free space - still shows as 100% used up... |
Beta Was this translation helpful? Give feedback.
Only the workflow is defined in your repository. The actions listed in the error messages are owned by the actions and docker organizations. You can see that by the part in front of the first slash, e.g.
actions/checkout
refers to a repository that’s definitely not owned by you. 😉