Hello,
First of all thanks for the awesome work.
I've found out that forgejo-runner doesn't support "reusable workflows" (https://docs.github.com/en/actions/using-workflows/reusing-workflows) , which I believe is really helpful reducing code duplication across many repositories in a Forgejo instance.
I couldn't find any roadmap of planned features for the runner, so I'm filling this issue as feature request. Please let me know if there are better methods for tracking it.
example:
reusable.yml
name: Reusable workflow example
on:
workflow_call:
inputs:
config-path:
required: true
type: string
secrets:
token:
required: true
jobs:
reusable:
runs-on: docker
steps:
- run: |
echo == config-path: ${{ inputs.config_path }}
echo == repo-token: ${{ secrets.token }}
caller.yml
on: [ workflow_dispatch ]
jobs:
call-workflow-passing-data:
uses: ./reusable.yml
with:
config-path: ./somewhere/myconfig
secrets:
token: ${{ secrets.MYTOKEN}}
Hello, First of all thanks for the awesome work. I've found out that forgejo-runner doesn't support "reusable workflows" (https://docs.github.com/en/actions/using-workflows/reusing-workflows) , which I believe is really helpful reducing code duplication across many repositories in a Forgejo instance. I couldn't find any roadmap of planned features for the runner, so I'm filling this issue as feature request. Please let me know if there are better methods for tracking it. example: reusable.yml ``` name: Reusable workflow example on: workflow_call: inputs: config-path: required: true type: string secrets: token: required: true jobs: reusable: runs-on: docker steps: - run: | echo == config-path: ${{ inputs.config_path }} echo == repo-token: ${{ secrets.token }} ``` caller.yml ``` on: [ workflow_dispatch ] jobs: call-workflow-passing-data: uses: ./reusable.yml with: config-path: ./somewhere/myconfig secrets: token: ${{ secrets.MYTOKEN}} ```