Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get on github marketplace #58

Open
maxheld83 opened this issue Feb 11, 2019 · 2 comments
Open

get on github marketplace #58

maxheld83 opened this issue Feb 11, 2019 · 2 comments
Assignees
Labels
blocked github Related to / requiring support from github (actions)

Comments

@maxheld83
Copy link
Owner

currently blocked, because multi-action repos are not yet supported

@maxheld83 maxheld83 added blocked github Related to / requiring support from github (actions) labels Feb 11, 2019
@maxheld83 maxheld83 self-assigned this Feb 14, 2019
@maxheld83
Copy link
Owner Author

I just tried to poke this by adding a release, but it's still not working, so I guess there's still no support for multi-action repos on GitHub actions marketplace.

@maxheld83
Copy link
Owner Author

I aksed GitHub on Feb 2 about this:

thanks for the invite to the "staff ship" thing. I did publish my deploy to gh-pages action: https://github.com/marketplace/actions/github-pages-deploy

The E-Mail you send mentioned that there has to be a Dockerfile at the repo root. I'm wondering how this would work for repos that have multiple (interrelated) actions.

Specifically, I'm building another repo with lots of actions for the R platform for statistical computing, and there, the individual actions and their Dockerfiles are all in repo/action-foo/. I vaguely remember that the gh action docs recommend that such related actions be grouped in one repo (sorry, can't find the source).

The latter seems to make more intuitive sense to me; otherwise I worry I'd need to deal with submodule (and who wants that?).

Some guidance on this would be much appreciated.

Response was that this was actively being worked on.

Alternative is, I guess, to use submodules (arghh :()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked github Related to / requiring support from github (actions)
Projects
None yet
Development

No branches or pull requests

1 participant