# GitHub Actions Published articles for GitHub Actions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Publishing a Kubernetes SIG's Images to registry.k8s.io DevFeed: [Publishing a Kubernetes SIG's Images to registry.k8s.io]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-09-16T18:00:00Z Content type: tutorial Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [container images](), [GitHub Actions](), [CI/CD](), [Google Cloud Platform (GCP)]() Tags: [ci-cd](), [container-image](), [container-image-registry](), [container-images](), [documentation](), [github-actions](), [google-cloud](), [guide](), [kubernetes]() ### AI overview A guide to publishing official Kubernetes SIG container images through registry.k8s.io. It explains why GHCR is unsuitable for public distribution and describes the ordered workflow involving Prow, Google Cloud Build, staging registries, and image promotion. ### Source excerpt If you're publishing container images for a Kubernetes SIG project, you might expect the same publishing workflow used by other container registries to work. That was my assumption too. My workflow successfully published the images, but they weren't publicly available. Instead, official Kubernetes project images are distributed through registry.k8s.io , the Kubernetes project's official container image registry. No single step was hard, but the steps were spread across multiple repositories and had to happen in a particular order, something I mostly learned by tripping over them. This post is the guide I wish I had at the start. It walks through that workflow end to end using Cluster Inventory API from SIG Multicluster as an example. The same process applies to eligible Kubernetes subprojects that publish official container images. My first attempt: GHCR I first tried a common GitHub release pattern: using GitHub Actions to publish images to ghcr.io on a tag push (cluster-inventory-api#40 ). The workflow succeeded, but Kubernetes GitHub organizations keep GHCR packages private, so GHCR cannot be used for public distribution. As described in the registry.k8s.io documentation , official images take a different route: Prow (the Kubernetes project's CI/CD system) picks up a tag push and runs Google Cloud Build on Kubernetes-owned infrastructure to push the image to a staging registry, and the image promoter then copies it to registry.k8s.io. The first-time setup, step by step Besides the image-owning repository, this touches three infrastructure repositories: kubernetes/k8s.io , kubernetes/test-infra , and kubernetes/org . The pieces depend on each other like this: Before you start: decide your project details Before setting up the publishing workflow, decide a few project-specific details. These values will be reused throughout the setup when creating the staging registry, configuring image builds, and setting up image promotion: , which determines the staging ## Learn How to Deploy, Secure, and Automate Full-Stack Web Apps DevFeed: [Learn How to Deploy, Secure, and Automate Full-Stack Web Apps]() Original publisher: [Read original article]() Author: Beau Carnes Published: 2026-09-16T15:28:18Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [web applications](), [Deployment](), [CI/CD](), [FastAPI](), [GitHub Actions](), [Vue.js](), [nginx](), [firewalls](), [Python](), [Cloudflare](), [SSL](), [Ubuntu]() Tags: [analysis](), [authentication](), [ci-cd](), [deploy](), [fastapi](), [full-stack](), [github-actions](), [how-to](), [web](), [web-apps](), [youtube]() ### AI overview This article introduces an 11-hour freeCodeCamp course on deploying, securing, and automating a Vue.js and FastAPI web application. It covers Ubuntu server setup, SSH hardening, firewalls, application runtimes, Meilisearch, DNS, SSL, Nginx, Cloudflare, GitHub Actions, security testing, and observability. ### Source excerpt Taking a web application from local development to a live, secure production environment can be daunting if you've never looked under the hood. We just published a comprehensive course on the freeCode ## Test GitHub Actions Locally with Act DevFeed: [Test GitHub Actions Locally with Act]() Original publisher: [Read original article]() Author: Valerie Nielson Published: 2026-09-16T12:00:44Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [GitHub Actions](), [CI/CD](), [Docker](), [Testing](), [unit test]() Tags: [ci-cd](), [developer-tools](), [docker](), [github](), [github-actions](), [pull-request](), [testing](), [unit-test](), [workflow]() ### AI overview This tutorial explains how to test GitHub Actions workflows locally with act. It describes how act uses Docker to reproduce the workflow environment, including environment variables and the file system, and demonstrates testing pull-request workflows and unit tests before merging. ### Source excerpt GitHub Actions are a great way to implement CI/CD into your projects, whether personal or professional. GitHub has a lot of great tools to help with CI/CD, but GitHub Actions in particular is very helpful. However, writing actions can be tedious and a little annoying, especially if you don't know what you're doing. On top [...] The post Test GitHub Actions Locally with Act appeared first on Atomic Spin. ## Marketing ops as code: Automating events from planning to follow-up on GitHub DevFeed: [Marketing ops as code: Automating events from planning to follow-up on GitHub]() Original publisher: [Read original article]() Author: Tomoko Tanaka Published: 2026-09-11T18:26:10Z Content type: tutorial Language: en Sources: [GitHub Engineering]() Topics: [AI-assisted coding]() Tags: [ai-ml](), [api](), [automation](), [cli](), [events](), [github](), [github-actions](), [github-copilot](), [github-issues]() ### AI overview A GitHub marketing lead describes using GitHub Copilot and GitHub Actions to automate event operations from a GitHub Issue, including setup, daily registrant processing, and post-event cleanup. ### Source excerpt If you can write down how you do your work, you can automate it. Here's what I did to support GitHub's APAC marketing team. The post Marketing ops as code: Automating events from planning to follow-up on GitHub appeared first on The GitHub Blog. ## Any Nix package, live in your browser DevFeed: [Any Nix package, live in your browser]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-10T23:44:15Z Content type: article Language: en Sources: [Simon Willison's Weblog]() Topics: [Nix](), [WebAssembly](), [qemu](), [x86](), [GitHub Actions](), [Pull Request]() Tags: [browser](), [code-review](), [code-review-16](), [github-actions](), [github-actions-72](), [linux](), [linux-54](), [qemu](), [webassembly](), [webassembly-131](), [x86]() ### AI overview The article describes trynix.dev, which runs an x86_64 Linux virtual machine in the browser using qemu-wasm and WebAssembly. It can boot Nix packages from the past 13 years, including Python 3.6.2, and supports URL-addressable interactive shells. It also highlights trynix-preview, a GitHub Action that links pull requests to browser-based builds without servers. ### Source excerpt Any Nix package, live in your browser Farid Zakaria calls this his "magnum opus of Nix work", and I can see why. trynix.dev provides a qemu-wasm powered x86_64 Linux virtual machine running entirely in your browser through WebAssembly. That VM can then be booted with any Nix package from the past 13 years. They are URL addressable, so you can navigate to this page: https://trynix.dev/?pkg=python3%403.6.2 Then click "Load" and get an interactive shell against a virtual machine running Python 3.6.2 from 2017. Farid is building all sorts of neat things on top of this. One recent example: Review a pull request by booting it introduces trynix-preview, described like this: GitHub action that comments a link on a pull request which lets you boot the PR's build in the browser using https://trynix.dev. No servers, just browsers. Via Lobste.rs Tags: code-review, linux, webassembly, github-actions ## GitHub availability report: August 2026 DevFeed: [GitHub availability report: August 2026]() Original publisher: [Read original article]() Author: Jakub Oleksy Published: 2026-09-10T02:05:17Z Content type: article Language: en Sources: [GitHub Engineering]() Topics: [GitHub](), [site-reliability-engineering](), [migration](), [MySQL](), [GitHub Actions]() Tags: [availability](), [azure](), [company-news](), [database](), [github](), [github-actions](), [github-availability-report](), [migration](), [monitoring](), [mysql](), [news-insights](), [outage](), [performance](), [production]() ### AI overview GitHub reports five August incidents with degraded service performance and describes capacity, resiliency, database, Azure migration, and GitHub Actions improvements. ### Source excerpt In August, we experienced five incidents that resulted in degraded performance across GitHub services. The post GitHub availability report: August 2026 appeared first on The GitHub Blog. ## Automated Worker Versioning with GitHub Actions DevFeed: [Automated Worker Versioning with GitHub Actions]() Original publisher: [Read original article]() Author: Adam Quan Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [GitHub Actions](), [CI/CD](), [Deployment](), [Orchestration]() Tags: [automation](), [ci-cd](), [ci-cd-pipeline](), [deployment](), [github-actions](), [how-to](), [temporal-voices]() ### AI overview This tutorial explains how to automate Temporal Worker Versioning in a CI/CD pipeline with GitHub Actions and Worker Controller. It covers deterministic Workflow code changes, deployment versions, traffic ramping, pinned and auto-upgrade Workflows, safer rollouts, and rollbacks. ### Source excerpt Learn how to automate Temporal Worker Versioning in CI/CD with GitHub Actions and Worker Controller for safer rollouts, traffic ramping, and rollbacks. ## Distributed tracing for CI pipelines without touching a single workflow file DevFeed: [Distributed tracing for CI pipelines without touching a single workflow file]() Original publisher: [Read original article]() Author: George Sims, downtherabbithole.dev Published: 2026-09-08T11:00:00Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [ci]() Tags: [blog](), [ci](), [github](), [github-actions](), [instrumentation](), [jobs](), [opentelemetry](), [tracing](), [workflow](), [workflows]() ### AI overview The article describes collecting GitHub Actions events at the organization level and converting them into OpenTelemetry spans to trace CI workflows without editing individual workflow files. ### Source excerpt You've probably felt this one: GitHub Actions usage creeps up across your org, and your actual visibility into it doesn't keep pace. Which workflows are slow? Which are flaky? How long are jobs sitting queued for... ## MUST READ: Git - Going Pro DevFeed: [MUST READ: Git - Going Pro]() Original publisher: [Read original article]() Published: 2026-09-01T05:31:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Git](), [GitHub](), [GitHub Actions](), [ssh](), [Pull Request](), [Command-line interface]() Tags: [article](), [blog](), [cli](), [git](), [github](), [github-actions](), [reviews](), [ssh](), [worth-reading]() ### AI overview A recommendation for Tony Mattke's "Going Pro" article, which covers Git fundamentals and professional practices including SSH keys, pre-commit hooks, GitHub Actions, linting, branch protection, pull-request reviews, and the gh CLI. ### Source excerpt I sure wish Tony Mattke had started publishing his Git-related blog posts in 2017 when I was still struggling with the basics. In his latest Going Pro article he covers: Using SSH keys with Git and GitHub Pre-commit hooks GitHub Actions and linting GitHub Branch protection PR reviews gh CLI Absolutely worth every second you'll spend reading the article! ## Your alt text passes automated checks. That doesn't mean it's any good. DevFeed: [Your alt text passes automated checks. That doesn't mean it's any good.]() Original publisher: [Read original article]() Author: Taarik Ashenafi Published: 2026-08-24T20:56:32Z Content type: article Language: en Sources: [GitHub]() Topics: [Accessibility](), [alt text](), [GitHub](), [Tooling]() Tags: [accessibility](), [alt-text](), [automation](), [blog](), [engineering](), [false-positives](), [github](), [github-actions](), [plugin](), [scanner](), [user-experience]() ### AI overview This article explains a GitHub Accessibility Scanner plugin for evaluating alt text. It distinguishes deterministic checks that automated tools can prove from contextual quality judgments that may require a model and image context. ### Source excerpt We built a plugin for the GitHub Accessibility Scanner to make sure your alt text is actually accessible. Here's how it works. The post Your alt text passes automated checks. That doesn't mean it's any good. appeared first on The GitHub Blog. ## Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain DevFeed: [Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain]() Original publisher: [Read original article]() Author: Yaron Avital Published: 2026-08-21T23:00:21Z Content type: article Language: en Sources: [Unit 42]() Topics: [sdlc](), [Security](), [Application Security](), [CI/CD](), [GitHub Actions](), [npm](), [Bun](), [Python](), [Claude Code](), [vs-code](), [Claude](), [Ethereum]() Tags: [blockchain](), [c2](), [chaindrop](), [ci-cd](), [claude-code](), [general](), [github-actions](), [insights](), [malware](), [npm-packages](), [persistence](), [python](), [sdlc](), [security](), [software-supply-chain-attack](), [supply-chain](), [vs-code]() ### AI overview Unit 42 describes how software supply-chain attackers are targeting developer tools, CI/CD pipelines, accounts, packages, setup scripts and developer environments before software reaches production. It examines the ChainDrop npm worm, which used malicious preinstall hooks, a Bun runtime, an obfuscated payload, Python-based memory theft, stolen tokens and secrets, self-propagation, persistence in VS Code and Claude Code, and Ethereum-managed command-and-control infrastructure. ### Source excerpt Attackers are targeting CI/CD pipelines and developer tools instead of application code, requiring total SDLC visibility and strict security controls The post Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain appeared first on Unit 42. ## Running AI agents in GitHub Actions with Docker Sandboxes DevFeed: [Running AI agents in GitHub Actions with Docker Sandboxes]() Original publisher: [Read original article]() Author: Jennifer Kohl Published: 2026-08-21T13:00:00Z Content type: tutorial Language: en Sources: [Docker]() Topics: [AI-assisted coding](), [ci]() Tags: [ai-agent](), [ai-coding](), [ci](), [docker](), [docker-sandboxes](), [engineering](), [github-actions](), [postgresql](), [pull-requests](), [sandboxes](), [testcontainers]() ### AI overview A tutorial on running AI coding agents in GitHub Actions inside Docker Sandboxes, emphasizing isolated execution while agents run tests, fix a seeded bug, and open a draft pull request. ### Source excerpt Run AI agents in GitHub Actions with Docker Sandboxes. See how isolated agents can run Testcontainers tests, fix code, and open draft pull requests. ## Stop burning tokens on code review DevFeed: [Stop burning tokens on code review]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-08-15T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Code review](), [Claude Code](), [Code](), [GitHub Actions](), [Architecture & Design](), [cursor]() Tags: [agents](), [claude-code](), [code](), [code-review](), [cursor](), [engineering](), [github-actions](), [security]() ### AI overview The author argues that custom linters can provide fast, inexpensive guardrails and feedback loops for both human and agent-written code. They describe mixed experiences with Cursor's BugBot and Claude code review skills, especially the high noise and review burden produced when those skills run in GitHub Actions. ### Source excerpt I've been experimenting with different approaches to build a system where humans and agents can ship fast safely. Think I've found something that works - custom linters. ## Generating AI Descriptions of Automated Pull Requests DevFeed: [Generating AI Descriptions of Automated Pull Requests]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [GitHub Copilot CLI](), [GitHub Actions](), [GitHub Copilot](), [Large Language Model](), [Ruby](), [Slack](), [changelog](), [Pull Request](), [Open Source](), [JSON](), [YAML]() Tags: [ai](), [automated](), [changelog](), [ci](), [cli](), [copilot](), [github](), [github-actions](), [github-copilot](), [github-copilot-cli](), [json](), [llm](), [open-source](), [pull-request](), [pull-requests](), [ruby](), [yaml]() ### AI overview A tutorial explains how the maintainer of the slack-ruby-client library uses a scheduled GitHub Actions workflow and GitHub Copilot CLI to generate meaningful commit messages, pull request bodies, and CHANGELOG entries from diffs of regenerated Slack API code. It also covers YAML indentation, prompt files, response logging, and extracting a JSON result from Copilot CLI output. ### Source excerpt The slack-ruby-client library, an open source Ruby gem I maintain, runs a scheduled GitHub Actions workflow that regenerates code from Slack's API definitions and opens a pull request with the diff. The commit message and CHANGELOG entry used to be a generic "Update API (2026-08-11)", which told a reviewer nothing about what actually changed. Here's how we taught the workflow to describe its own diffs, using GitHub Copilot CLI, which open source maintainers can get for free. The Idea The workflow already computes a diff before opening the pull request. Instead of a boilerplate commit message, we pipe that diff through an LLM and ask it to summarize what changed, then use the response as the commit message and PR body. - name: Check for changes id: changes run: | if git diff --quiet; then echo "changed=false" >> "$GITHUB_OUTPUT" else echo "changed=true" >> "$GITHUB_OUTPUT" fi - name: Prepare diff for AI summary if: steps.changes.outputs.changed == 'true' run: | git diff --stat | sed 's/^/ /' > /tmp/diff_stat.txt git diff | head -c 20000 | sed 's/^/ /' > /tmp/diff.txt The sed 's/^/ /' indent isn't decorative. actions/ai-inference substitutes template variables as raw text into a prompt YAML file before parsing it, so a multi-line diff starting at column 0 breaks the indentation of the enclosing content: |- block scalar. Pre-indenting the file to match keeps the YAML valid no matter what the diff looks like. The Prompt File actions/ai-inference supports .prompt.yml files, a small convention for keeping the system/user prompt out of the workflow YAML. messages: - role: system content: |- You write CHANGELOG entries describing an automated API update to slack-ruby-client, a Ruby gem whose Web API endpoint methods, argument validations, specs, and bin commands are code-generated from vendored Slack API method definitions (via a git submodule and rake task). Given a diffstat and a diff of the regenerated files, respond with ONLY a single JSON object (no markdown code fence ## Port's Integration Catalog: 200+ Tools for Your Context Lake DevFeed: [Port's Integration Catalog: 200+ Tools for Your Context Lake]() Original publisher: [Read original article]() Author: Alina Barenboim Published: 2026-08-10T16:27:08Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [CI/CD](), [Kubernetes](), [GitHub](), [Provisioning](), [incident management](), [Application Performance Management (APM)](), [Security](), [Code review](), [Deployment](), [DevOps](), [GitHub Actions](), [GitLab]() Tags: [apm](), [ci-cd](), [deployment](), [devops](), [git](), [github](), [github-actions](), [gitlab](), [incident-management](), [jenkins](), [kubernetes](), [review](), [security](), [vulnerabilities]() ### AI overview Port's Integration Catalog describes more than 200 integrations that unify engineering-tool data in a queryable Context Lake. It covers Git, Kubernetes, CI/CD, incident management, APM, security scanning, service mesh, policy violations, deployments, build results, and code activity, with support for custom integrations through Ocean, connectors, APIs, events, and MCPs. ### Source excerpt Explore Port's 200+ integrations across CI/CD, Kubernetes, incident management, security, and more, all feeding one Context Lake. ## ChainDrop npm Worm: Why SLSA Provenance Wasn't Enough DevFeed: [ChainDrop npm Worm: Why SLSA Provenance Wasn't Enough]() Original publisher: [Read original article]() Author: Harness Team Published: 2026-08-10T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [ChainDrop](), [npm](), [supply-chain-security](), [Malware](), [npm packages](), [GitHub Actions](), [GitHub]() Tags: [chaindrop](), [ci](), [ci-cd](), [github](), [github-actions](), [integrity](), [least-privilege](), [malware](), [npm](), [npm-worm](), [openid-connect](), [provenance](), [security](), [slsa](), [software-supply-chain-security](), [worm]() ### AI overview The ChainDrop npm worm compromised hundreds of packages while retaining valid SLSA provenance, demonstrating that build attestations do not guarantee source integrity. The article explains the worm's propagation, credential theft, persistence mechanisms, and recommended defenses, including source governance, dependency controls, least-privilege identities, policy gates, and runtime evidence. ### Source excerpt ChainDrop poisoned hundreds of npm packages while retaining valid provenance. Learn why signed builds need source governance, policy gates, and runtime evidence | Blog ## ChainDrop: Inside a Self-Propagating npm Worm DevFeed: [ChainDrop: Inside a Self-Propagating npm Worm]() Original publisher: [Read original article]() Author: Unit 42 Published: 2026-08-06T22:26:39Z Content type: article Language: en Sources: [Unit 42]() Topics: [ChainDrop](), [npm](), [Malware](), [C2](), [Ethereum](), [GitHub Actions](), [GitHub](), [CI/CD](), [Security]() Tags: [blockchain](), [c2](), [chaindrop](), [ci](), [claude-code](), [developer-tooling](), [ethereum](), [github](), [github-actions](), [high-profile-threats](), [infrastructure](), [malware](), [security](), [ssh](), [supply-chain](), [tokens]() ### AI overview This article analyzes ChainDrop, a self-propagating npm worm that infected more than 400 packages and threatened developer workstations, CI pipelines, cloud environments and downstream users. It describes credential and token theft, GitHub Actions runner memory extraction, package republishing, persistence through developer and AI coding tools, blockchain-based C2 resolution, and C2 reconfiguration through an Ethereum transaction. ### Source excerpt Analysis of ChainDrop, an npm supply chain worm extracting GitHub Actions runner secrets and using Ethereum smart contracts for C2 routing. The post ChainDrop: Inside a Self-Propagating npm Worm appeared first on Unit 42. ## CI Doesn't Need On-Demand: Moving Our Build Pipelines to Spot Instances DevFeed: [CI Doesn't Need On-Demand: Moving Our Build Pipelines to Spot Instances]() Original publisher: [Read original article]() Author: Yuvraj Singh Singhel Published: 2026-08-05T15:07:35Z Content type: article Language: en Sources: [Razorpay Engineering - Medium]() Topics: [CI/CD](), [GitHub Actions](), [Kubernetes](), [Amazon Web Services]() Tags: [aws](), [ci](), [ci-cd](), [github-actions](), [kubernetes](), [pipelines](), [self-healing]() ### AI overview Razorpay describes a self-healing infrastructure layer for GitHub Actions on Kubernetes that runs most CI workloads on AWS Spot Instances. The system detects spot-node termination, retries jobs, and cleans up orphaned pods; the article states that 80% of CI workloads run on spot instances with a 99.2% job success rate. ### Source excerpt Contributors: Guptaanuj CI/CD pipelines have always had a money-vs-stability problem. Run on-demand AWS instances and your build infrastructure is rock solid, expensive, and predictable. Run on spot instances and your costs drop 70-90%, but AWS can pull the rug with 2 minutes of warning. For most teams, this is a false choice. Either pay full price for reliability, or save money and accept that builds will fail in ways nobody can debug. At Razorpay, we stopped accepting that trade-off. We built a self-healing infrastructure layer for GitHub Actions on Kubernetes that runs 80% of our CI workloads on spot instances while maintaining a 99.2% job success rate. When AWS terminates a spot node mid-build, our system detects it, retries the job, cleans up the orphaned pods, and the developer never knows. This is the story of what we built, why polling wasn't an option, and the war stories that taught us how to do retries without burning everything down. The Problem With Spot Instances On CI Spot instances are AWS capacity that nobody else wants right now. The pricing is brutal compared to on-demand: a c5.2xlarge that costs around $0.34/hour on-demand drops to roughly $0.08/hour on spot. For workloads like CI/CD, where jobs are short-lived and parallelizable, the math is obvious. The catch is in the contract. AWS reserves the right to take spot capacity back at any moment, with a 2-minute warning. That works for some workloads. For others, it's catastrophic. GitHub Actions runners on Kubernetes is the hard case. A typical CI job goes like this: GitHub assigns the job to a runner. The runner is a pod on a Kubernetes cluster running on an AWS Spot instance. The job downloads dependencies, runs tests, builds artifacts. The runner reports back to GitHub. Now insert a spot termination at minute 4 of a 7-minute build. What happens? The runner pod dies mid-job. GitHub never gets a completion signal; the job hangs until timeout, then marks as "failed". A new runner pod gets schedule ## How to Use GitHub Actions to Deploy to Kubernetes Without Shared Secrets DevFeed: [How to Use GitHub Actions to Deploy to Kubernetes Without Shared Secrets]() Original publisher: [Read original article]() Author: info@goteleport.com (Noah Stride) Published: 2026-08-05T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [GitHub Actions](), [Kubernetes](), [Security](), [sensitive data](), [Vulnerabilities]() Tags: [ci-cd](), [github](), [github-actions](), [how-to](), [kubernetes](), [secrets](), [security](), [sensitive-data]() ### AI overview This tutorial explains how to use Teleport and GitHub Actions to deploy applications to Kubernetes without shared, long-lived credentials. It covers short-lived identities, Kubernetes RBAC, Teleport roles, and join tokens, and discusses extending the approach to database connections and internal APIs. ### Source excerpt Learn how use GitHub Actions to deploy to Kubernetes using short-lived, verifiable identities. ## GitHub agentic workflows and Renovate DevFeed: [GitHub agentic workflows and Renovate]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Nicolas Fränkel]() Topics: [GitHub](), [GitHub Actions]() Tags: [agentic-workflow](), [dependencies](), [github](), [github-actions](), [github-agentic-workflows](), [pull-requests](), [renovate](