Click any tag below to further narrow down your results
Links
The article critiques GitHub Actions, highlighting its inefficiencies and frustrations, particularly with its log viewer, YAML configuration, and marketplace risks. The author, with extensive CI experience, argues that while GitHub Actions has widespread use, it often complicates rather than simplifies the development process.
The article discusses the need to optimize websites for AI agents, which prefer structured content like Markdown. It explains how the author modified their blog to serve Markdown files alongside HTML, using a GitHub Actions workflow for deployment. The piece raises questions about content usage by AI but suggests it may lead to better attribution.
The Guardian's engineering team switched from GitHub-hosted runners to self-hosted ones to improve build speed and reduce costs. They detail the challenges faced during the transition and the benefits gained, such as greater control over build environments and a significant drop in monthly expenses.
This article outlines four orchestration levels for data workflows, from simple cron jobs to full orchestration systems like Prefect. It emphasizes that teams should choose tools based on their project's maturity and specific needs, rather than following trends or trying to adopt complex solutions prematurely.
This article details LinkedIn's efforts to upgrade its Static Application Security Testing (SAST) capabilities. It covers the challenges faced with legacy systems, the design principles guiding the modernization, and the implementation of a new GitHub Actions-based workflow to enhance security without disrupting developer productivity.
Aikido Security has identified a vulnerability in GitHub Actions and GitLab CI/CD workflows that allows AI agents to execute malicious instructions, potentially leaking sensitive information. The flaw affects multiple companies and demonstrates how AI prompt injection can compromise software supply chains.
pinact is a command-line tool that helps you edit and pin versions of GitHub Actions and reusable workflows. It allows you to update versions, verify annotations, and create pull request reviews for better security and reliability in CI/CD pipelines.
This article outlines how to deploy microservices using Azure Kubernetes Service (AKS) automated through GitHub Actions. It covers the necessary prerequisites, the CI/CD pipeline stages, and best practices for a successful deployment. You’ll learn how to set up the process for building, pushing, and deploying Docker images effectively.
Recent security issues with GitHub Actions involved the modification of the tj-actions/changed-files action, which leaked secrets. To mitigate such vulnerabilities, the author recommends pinning versions to explicit commit hashes and introduces a tool called "just an installer" (jas) that verifies downloads using SHA-256 hashes, enhancing the reliability of binary installations in GitHub Actions workflows.
AWS Lambda now integrates with GitHub Actions, allowing automatic deployment of Lambda functions whenever code changes are pushed to GitHub repositories. This new feature simplifies the CI/CD process by eliminating the need for custom scripts and manual configurations, supporting both .zip file and container image deployments while streamlining permissions and error handling.
The GitHub Actions `attest-build-provenance` action allows users to generate signed attestations for workflow artifacts, binding them to a SLSA build provenance predicate. It utilizes the Sigstore service for signing, supports both public and private repositories, and facilitates verification through the GitHub CLI, ensuring artifact integrity and provenance.
The article discusses how the team automated updates for GitHub Actions runners using Claude AI, enabling seamless management and deployment of updates. This automation significantly reduces manual intervention and streamlines their workflow, enhancing overall efficiency in their development process.
Claude Code provides a simple command wrapper for integrating with various AI providers like OpenAI, Google, and xAI. It allows users to easily switch models and customize settings, enhancing compatibility with GitHub Actions and optimizing for OpenAI's gpt-5 series. The tool also supports setting custom endpoints and spawning an HTTP server for seamless interactions with different AI SDKs.
Hosting GitHub Actions runners on HashiCorp Nomad offers a lightweight and scalable alternative to Kubernetes, enabling organizations to run self-hosted runners within their private networks for enhanced security and control. This solution reduces operational costs, simplifies management, and improves deployment speed by utilizing ephemeral runners that minimize resource overhead and ensure clean environments for each job. Additionally, it supports multi-cloud and hybrid deployments, allowing for flexible infrastructure management without vendor lock-in.
Researchers discovered vulnerabilities in the Nix ecosystem related to GitHub Actions, specifically concerning the pull_request_target event, which could allow for supply chain attacks and command injection. They identified two significant flaws: one involving xargs and the other enabling symbolic link exploitation, leading to unauthorized access to sensitive data. The maintainers acted quickly to disable the vulnerable workflows and implement fixes.
The project provides tools in Go for automated testing against Fastly's WAF simulator, incorporating a CI/CD pipeline with GitHub actions to run tests on code changes. Test cases are structured in YAML format within the test/rules directory, detailing various fields such as identifiers, requests, expected responses, and signals. Users must set up their Fastly NGWAF credentials, run Terraform commands, and check workflow statuses on GitHub to ensure the WAF rules function correctly.
Blacksmith has successfully reverse-engineered the internals of GitHub Actions cache to create a more efficient caching solution that can deliver cache speeds up to 10 times faster for users, all without requiring any code changes to existing workflows. By implementing a transparent proxy system and leveraging their own object storage, they achieved significant performance improvements while simplifying the user experience.
Learn how to capture screenshots of a statically exported Next.js site using a GitHub Actions workflow, especially when preview deployments are not available. The article outlines a script utilizing Puppeteer to automate the screenshot process for each page during pull requests. Additionally, it provides details on setting up the workflow to build the app, serve it, and upload the screenshots as artifacts for review.
Grafana Labs introduced Zizmor, an open source static analysis tool, in their CI/CD pipelines to detect and prevent vulnerabilities in GitHub Actions following a security incident. The tool helps identify unsafe configurations and practices, such as the use of `pull_request_target`, and is part of a broader effort to enhance security across their repositories. Despite facing challenges like GitHub's rate limiting, Grafana is committed to using Zizmor to bolster their defenses against future attacks.
Gemini CLI GitHub Actions is an AI-powered tool designed to enhance team collaboration in software development by automating routine coding tasks and facilitating issue triage and pull request reviews. Available in beta, it allows developers to delegate tasks easily using the @gemini-cli tag and offers robust security features to ensure safe operation in repositories. The tool is open-source, customizable, and encourages community contributions to enhance its workflows.
GitHub Actions allows users to specify any executable on the $PATH as the shell for running commands, rather than being limited to predefined shell values. This flexibility enables various unconventional uses, such as executing C code directly or modifying the $PATH dynamically. However, this raises potential security concerns, as it allows for unexpected behaviors in the execution environment.
The article discusses the security considerations necessary for using GitHub Actions in CI/CD setups, emphasizing the importance of protecting workflows against potential threats from contributors with write access. It details various attack scenarios, including script injection vulnerabilities, and provides best practices for securing sensitive workflows and managing permissions effectively.
AWS has introduced a new feature that allows for the deployment of AWS Lambda functions directly through GitHub Actions, simplifying the CI/CD process with a declarative YAML configuration. This improvement eliminates the need for manual packaging and configuration steps, enhancing developer experience and security through seamless IAM integration. Users can easily set up a workflow to automatically deploy their functions with minimal effort.
Sysdig's Threat Research Team uncovered significant security vulnerabilities in GitHub Actions workflows across popular open source projects, including those by MITRE and Splunk. Their research revealed how insecure configurations, particularly using pull_request_target, can expose sensitive credentials and allow for exploitation, prompting the team to recommend best practices to enhance CI/CD security.