GitHub Actions secret
A GitHub Actions secret is an encrypted repository, environment, or organization value that workflows can access without exposing its contents.
.NET MAUI in Action
A GitHub Actions secret is an encrypted repository, environment, or organization value exposed to workflows without revealing its stored content.
- How it is used
- Protects signing and store-upload credentials while deployment workflows build, sign, and publish Android and iOS apps.
- How deep it goes
- Demonstrates preparing, uploading, referencing, decoding, and applying text and base64-encoded file secrets in workflow commands.
- Examples
- Uses Android keystores, iOS certificates and provisioning profiles, a Google service-account JSON file, and App Store Connect API keys.
- What you can do after
- Apply it via GitHub Actions by storing deployment credentials and referencing them in signing and store-upload steps.
Read how .NET MAUI in Action explains GitHub Actions secret →
Road to Kubernetes
A GitHub Actions secret is an encrypted repository-scoped value that workflows can access without exposing its contents in source code or logs.
- How it is used
- Keeps deployment credentials and settings outside workflow source while making them available to GitHub Actions jobs.
- How deep it goes
- Walks through repository setup and workflow use, then flags dotenv transfer encryption as outside scope.
- Examples
- Uses an NGINX installation workflow, Docker Hub image publishing, and a generated production dotenv file.
- What you can do after
- Operate/configure it by storing repository values, referencing them in workflows, and checking that secret names match.
Read how Road to Kubernetes explains GitHub Actions secret →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
A GitHub secret is an encrypted repository or organization value that GitHub Actions workflows can access without exposing its underlying credential or configuration value.
- How it is used
- Supplies sensitive registry and Kubernetes values to a GitHub Actions deployment workflow without putting them in deployment code.
- How deep it goes
- Walks through preparing values, adding repository secrets, referencing them in YAML, and checking failures; does not detail GitHub’s storage internals.
- Examples
- Uses registry credentials, a Base64-encoded kubeconfig, and workflow YAML referencing secrets.KUBE_CONFIG and registry secret names.
- What you can do after
- Operate/configure it: add repository secrets and reference them from a deployment workflow’s environment variables or kubectl action.
Related concepts
- workflow definitionconfigures · A workflow definition is a declarative specification of an automated process’s tasks, their order or dependencies, and the conditions governing execution.
- sensitive informationuses · Sensitive information is information requiring protection because its unauthorized access, disclosure, alteration, or misuse could cause harm or violate obligations.
- private keyuses · A private key is the secret component of an asymmetric cryptographic key pair used by its holder for operations such as authentication, decryption, or digital signing.
- environment variableconfigures · An environment variable is a named value supplied through an operating-system or process environment and made available to programs for runtime configuration or information.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.