github-actions-workflows

You can create secure GitHub Actions workflows with OIDC authentication by using reusable templates that enforce least-privilege permissions and passwordless cloud identity. This skill provides ready-made templates automating OIDC setup for multi-cloud deployments without long-lived secrets.

Yes, you can build and push containers to GHCR using GitHub Actions with pinned dependencies. This skill provides GHCR container build and push patterns that strictly pin action SHAs and manage secrets for tamper-resistant CI/CD pipelines.

Deploying to Hetzner K3s using GitHub Actions is best achieved via SSH-based rollout patterns. This skill offers a deploy-k3s.yml template that automates secure, production-ready deployments to your Hetzner K3s cluster.

Yes, this GitHub Actions workflow approach supports Azure deployments through multi-cloud integration. The reusable templates apply OIDC authentication and security best practices to deploy your containers across Azure alongside Hetzner infrastructure.

You can audit and troubleshoot GitHub Actions permissions for governance by enforcing least-privilege access and reviewing pinned action SHAs. This skill includes guidance on auditing workflows, ensuring robust governance, and troubleshooting security misconfigurations.

You should avoid using reusable GitHub Actions workflow templates when your deployment target lacks support for OIDC or SSH-based rollout patterns. These templates are designed for multi-cloud environments like Azure and Hetzner K3s and may not fit custom deployment pipelines.