Skip to content

patch: Add Flowzone back #43

patch: Add Flowzone back

patch: Add Flowzone back #43

Workflow file for this run

name: Flowzone
on:
pull_request:
types: [opened, synchronize, closed]
branches: [main, master]
# allow external contributions to use secrets within trusted code
pull_request_target:
types: [opened, synchronize, closed]
branches: [main, master]
workflow_dispatch:
jobs:
flowzone:
name: Flowzone
uses: product-os/flowzone/.github/workflows/flowzone.yml@master
# prevent duplicate workflow executions for pull_request and pull_request_target
if: |
(
github.event.pull_request.head.repo.full_name == github.repository &&
github.event_name == 'pull_request'
) || (
github.event.pull_request.head.repo.full_name != github.repository &&
github.event_name == 'pull_request_target'
)
# Workflows in the same org or enterprise can use the inherit keyword to implicitly pass secrets
secrets: inherit
with:
balena_slugs: balenalabs/balenasound
update-balena-yml:
name: Update balena.yml
uses: balena-io-experimental/balena.yml-action@main

Check failure on line 36 in .github/workflows/flowzone.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/flowzone.yml

Invalid workflow file

invalid value workflow reference: references to workflows must be rooted in '.github/workflows'
with:
# Synchronise the GitHub README with the Balena Hub README
sync_readme: true
# If pushing a tag to deploy, use the same tag as the version number to display on Balena Hub
sync_tag: false