Support private repositories for GitHub Actions about toolkit HOT 10 CLOSED

At somepoint in the future we may support this but it is not on our near term backlog.

from toolkit.

You're correct that right now we don't support this yet, @chrispat what are our plans around this?

Note that right now you can reference an action from your own repo via relative paths. This provides some of the functionality private actions would bring (though admittedly not in a reusable way).

So for example, to reference an action that has its action.yml file in {repo root}/my-actions/action1, you could do the following in your workflow.yml - uses: ./my-actions/action1

from toolkit.

+1 for this. Pretty much every organization has multiple private repositories and being able to reuse in-house actions across those repositories is a must-have, in my opinion.

from toolkit.

One thing that has gotten me before (and may be what you're dealing with here) is that you need to run action/checkout before the action so that your source code makes it down to the right location.

from toolkit.

Glad I could help! Also added an internal PR to make that error a little more clear/point to checkout so hopefully it can be avoided by others going forward.

from toolkit.

It should support this spetially that we need some private configurations for jobs, and it is useless if I had to make tons of inputs for hardcoded staff like URL etc

from toolkit.

@damccorm I've tried moving our custom action in one of our private repositories as you suggested:
{repo root}/actions/action1/{here is where action.yml, src, lib and other files are}.

I also updated the uses in the workflow to uses: ./actions/action1 but I get the following error when the workflow runs:

##[error]Can't find 'action.yml' or 'Dockerfile' under '/home/runner/work/{org}/{repo}/actions/action1'.

Any ideas?

from toolkit.

That was it! Thank you @damccorm.

from toolkit.

Is there a plan to support this in the future?

from toolkit.

That's very disappointing to hear. We were planning to use GitHub actions in favor of Jenkins but since migrating the custom Jenkins plugins to GitHub actions that we were using will mean we'll have to make them public this is a dealbreaker so we'll have to stay on Jenkins from what it seems.

from toolkit.