github-actions-docs

GitHub Actions OIDC setup requires configuring workflow permissions and cloud provider trust relationships. The official docs provide the exact YAML syntax for defining id-token permissions and retrieving short-lived tokens using the GITHUB_TOKEN context.

Troubleshooting GitHub Actions reusable workflows involves checking the workflow_call trigger syntax and verifying the caller workflow path. Referencing the official docs helps identify structural mistakes in the called workflow YAML and caller job configuration.

GitHub-hosted runners provide pre-configured environments but do not support custom software or persistent setup like self-hosted runners. The GitHub Actions documentation clarifies the distinctions, limitations, and specific use cases for each runner type.

Managing secrets in GitHub Actions involves defining them at the repository or environment level and referencing them using the secrets context. The official documentation explains how to configure protected environments and securely pass encrypted values to jobs.

GitHub Actions workflow failures with GITHUB_TOKEN often stem from insufficient permissions defined in the workflow YAML. The official docs detail the default token permissions, required scopes for specific API calls, and how to modify the permissions key.