Ghost/.github/workflows/canary.yml

name: Canary Build
on: workflow_dispatch
env:
  FORCE_COLOR: 1
jobs:
  canary:
    uses: tryghost/actions/.github/workflows/canary.yml@main
    secrets: inherit
Extracted canary build to separate workflow no issue - by extracting it to a different workflow that uses the `workflow_dispatch` trigger, we can manually run a build, but also trigger it from Admin so we can always stay up-to-date 2021-06-01 19:04:16 +03:00			`name: Canary Build`
			`on: workflow_dispatch`
			`env:`
			`FORCE_COLOR: 1`
			`jobs:`
			`canary:`
Extracted Canary workflow to template refs https://github.com/TryGhost/actions/commit/4aee97472e172defe59258212ddb6e40e45591ca - the referenced commit copied the workflow file to our shared templates repository - this commit switches to using that template - this should help reduce duplication when we're doing v5 2022-03-31 10:27:18 +03:00			`uses: tryghost/actions/.github/workflows/canary.yml@main`
Allowed secrets to passthrough to re-usable workflow - this is needed so we can pass the secrets down the workflow chain 2023-04-20 10:52:29 +03:00			`secrets: inherit`