Support other github actions within composite github actions

Code to Cloud GitHub Actions
#1

I am trying to develop a private github action that runs on docker.
As a pre-condition to this action I want a step to checkout a repo.
In a workflow I would do it with

actions/checkout@v2

But as per the below description on composite Github Actions, the runs section does not support “uses”.
As a workaround, I have to invoke git clone which feels like a hack. Is there any plan to provide support for using other actions within composite actions ?

runs:
  using: "composite"
  steps:
    - run: echo Hello ${{ inputs.who-to-greet }}.
      shell: bash
    - id: random-number-generator
      run: echo "::set-output name=random-id::$(echo $RANDOM)"
      shell: bash
    - run: ${{ github.action_path }}/goodbye.sh
      shell: bash
1 Like
#2

There is an issue in the runner repository, but unfortunately it looks like it hasn’t been worked on since Summer 2020. Or at least nothing public, I wouldn’t know about anything in private.

1 Like
#3

I don’t see anything on our public roadmap related to adding support for “uses” statements in composite run actions at this time. Your “git clone” workaround is probably the best option right now. that, or build a javascript or container action instead.

#4

I went through this thread. None of it seems to solve the problem

#5

I see. It would be a requirement as time progresses. This is because orgs would want to build keep building complex Github Actions using the smaller lego blocks of github actions.
With git clone, is a simple workaround but not so for other actions.

#6

I’m aware of that, it was meant to answer the part of your question about whether there are plans to support uses: in composite actions. :wink:

1 Like
Action of actions?
#7

For those that stumble here from (insert search engine), uses and with are now live for composite actions, as per this announcement: GitHub Actions: Reduce duplication with action composition | GitHub Changelog

2 Likes
#8

I appreciate the update on the thread here, thanks @jethas-bennettjones

#9

Fwiw, in theory reusable workflows may address your requirements: