A reusable workflow lives in 'octo-org/workflows/.github/workflows/build.yml@v1'. What must be true for a private caller repository in the same org to use it?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Reusable workflows can be shared across repos. Private org sharing works when repository access and Actions sharing settings permit the caller to use that workflow source.
Full explanation below image
Full Explanation
GitHub Actions allows calling reusable workflows with uses: owner/repo/.github/workflows/file.yml@ref. Public reusable workflows can be called broadly; private reusable workflows can be shared within an organization or enterprise when access is granted (for example, the workflows repository visibility and org Actions permissions or access policies). It is not true that private reuse is impossible. Copy-pasting YAML defeats the purpose of reusable workflows. Reusable workflows are available on GitHub.com, not only GHES. Also remember the nesting limit for reusable workflow calls and that some features differ from composite actions. Callers may pass secrets explicitly or use secrets: inherit when appropriate for their trust model.