日本語のみで絞り込む
In the reusable workflow, use the inputs and secrets keywords to define inputs or secrets that will be passed from a caller workflow. on: workflow_call: inputs: ...
2022/3/18 -GitHub Actions simplifies using secrets with reusable workflows with the secrets: inherit keyword. Previously when passing secrets to a reusable ...
Use on.workflow_call to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more ...
2023/10/3 -To pass named inputs to a called workflow, use the with keyword in a job. Use the secrets keyword to pass named secrets. For inputs, the data ...
2026/2/21 -You set up your environments in GitHub, store secrets there, and expect them to be available when the workflow runs for the correct environment.
Workflows that call reusable workflows in the same organization or enterprise can use the inherit keyword to implicitly pass the secrets. I hope that doesn't ...
2026/2/13 -The reusable workflows docs explain that secrets: inherit implicitly passes secrets to the called workflow. And it does. At runtime, the called ...
2023/10/3 -You need to set the secret under the workflow call. Ie: on: workflow_call: secrets: PRIVATE_KEY: required: true inputs: ...
# reusabale workflow on: workflow_call ... The repository also contains recent GitHub Actions workflow runs to verify that the secrets remain masked throughout.
2026/9/22 -Validate secret inheritance, workflow_call inputs, GITHUB_TOKEN permissions, environment secrets, nesting, and cross-repository trust ...