<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitHub Actions on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/github-actions/</link><description>Recent content in GitHub Actions on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 3: Introduction to CI/CD - Automating Your Software Flow</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/introduction-ci-cd/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/introduction-ci-cd/</guid><description>&lt;h2 id="chapter-3-introduction-to-cicd---automating-your-software-flow"&gt;Chapter 3: Introduction to CI/CD - Automating Your Software Flow&lt;/h2&gt;
&lt;p&gt;Welcome back, future DevOps expert! In our previous chapters, we laid the groundwork by understanding the Linux command line and mastering version control with Git and GitHub. You now know how to manage code, track changes, and collaborate effectively. But what happens after you push your code to GitHub? How does it get built, tested, and eventually deployed to users?&lt;/p&gt;</description></item><item><title>AI for Automated Code Review and Quality Gates</title><link>https://ai-blog.noorshomelab.dev/ai-devops-guide-2026/ai-automated-code-review-quality-gates/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-devops-guide-2026/ai-automated-code-review-quality-gates/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow DevOps enthusiasts and AI adventurers! In our previous chapters, we laid the groundwork for integrating AI into the early stages of our development lifecycle. Now, we&amp;rsquo;re ready to dive into a truly transformative area: &lt;strong&gt;AI for Automated Code Review and Quality Gates&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Imagine a world where your code isn&amp;rsquo;t just checked for syntax errors, but intelligently analyzed for performance bottlenecks, subtle security vulnerabilities, and maintainability issues &lt;em&gt;before&lt;/em&gt; it even gets merged. This isn&amp;rsquo;t science fiction; it&amp;rsquo;s the power of AI at work, enhancing our code quality and ensuring our projects are robust from the get-go.&lt;/p&gt;</description></item><item><title>Chapter 4: Building CI/CD with GitHub Actions</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/github-actions-ci-cd/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/github-actions-ci-cd/</guid><description>&lt;h2 id="introduction-to-continuous-integration--github-actions"&gt;Introduction to Continuous Integration &amp;amp; GitHub Actions&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 4! In our journey through DevOps, we&amp;rsquo;ve explored the foundational elements of Linux, command-line mastery, and the power of Git for version control. Now, it&amp;rsquo;s time to elevate our development process by introducing &lt;strong&gt;Continuous Integration (CI)&lt;/strong&gt; and &lt;strong&gt;Continuous Delivery (CD)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;CI/CD is the backbone of modern software development. It&amp;rsquo;s about automating the build, test, and deployment phases of your application lifecycle, ensuring that your code is always in a releasable state. Imagine pushing a change, and automatically, your tests run, your application builds, and it&amp;rsquo;s ready to be deployed – that&amp;rsquo;s the magic of CI/CD! This automation drastically reduces manual errors, speeds up development cycles, and allows teams to deliver value faster and more reliably.&lt;/p&gt;</description></item><item><title>Smart CI: AI-Driven Testing and Build Optimization</title><link>https://ai-blog.noorshomelab.dev/ai-devops-guide-2026/smart-ci-ai-driven-testing-build-optimization/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-devops-guide-2026/smart-ci-ai-driven-testing-build-optimization/</guid><description>&lt;h2 id="introduction-supercharging-your-ci-with-ai"&gt;Introduction: Supercharging Your CI with AI&lt;/h2&gt;
&lt;p&gt;Welcome back, future-forward engineers! In previous chapters, we laid the groundwork for integrating AI and ML into DevOps, exploring MLOps principles and setting up our foundational tools. Now, it&amp;rsquo;s time to dive into the heart of software delivery: Continuous Integration (CI).&lt;/p&gt;
&lt;p&gt;Traditionally, CI pipelines run every test, every time, regardless of the changes made. While thorough, this can lead to slow feedback loops, wasted computational resources, and developer frustration, especially in large projects. What if your CI pipeline could be smarter? What if it could learn from past failures, understand the impact of code changes, and make intelligent decisions to optimize its own execution?&lt;/p&gt;</description></item><item><title>12. Integrating Testcontainers with CI/CD: GitHub Actions and GitLab CI</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/12-ci-cd-integration/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/12-ci-cd-integration/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our journey so far, you&amp;rsquo;ve mastered the art of using Testcontainers to create isolated, disposable environments for your integration tests locally. But what good are robust local tests if they can&amp;rsquo;t run just as reliably in your Continuous Integration/Continuous Deployment (CI/CD) pipeline? That&amp;rsquo;s precisely what we&amp;rsquo;re tackling in this chapter!&lt;/p&gt;
&lt;p&gt;Integrating Testcontainers into your CI/CD workflow is a critical step towards achieving truly reliable, automated testing. It ensures that your integration tests, which depend on external services like databases or message brokers, run in a consistent, clean environment every single time your code is pushed. This eliminates the dreaded &amp;ldquo;it works on my machine!&amp;rdquo; syndrome and boosts your confidence in deploying changes.&lt;/p&gt;</description></item><item><title>Chapter 12: Project 1: End-to-End CI/CD Pipeline for a Web Application</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/project-ci-cd-web-app/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/project-ci-cd-web-app/</guid><description>&lt;h2 id="chapter-12-project-1-end-to-end-cicd-pipeline-for-a-web-application"&gt;Chapter 12: Project 1: End-to-End CI/CD Pipeline for a Web Application&lt;/h2&gt;
&lt;p&gt;Welcome to your first major DevOps project! Up until now, we&amp;rsquo;ve explored individual tools and concepts: from the Linux command line to Git for version control, Docker for containerization, and the fundamentals of CI/CD. Now, it&amp;rsquo;s time to bring them all together and build something truly powerful: an &lt;strong&gt;End-to-End CI/CD Pipeline for a Web Application&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This chapter is your opportunity to apply everything you&amp;rsquo;ve learned in a practical, hands-on scenario. You&amp;rsquo;ll set up a complete workflow that automatically takes your code from a Git repository, builds it, tests it (conceptually for this project), containerizes it, and then prepares it for deployment. This automation is the heart of modern software delivery, enabling faster, more reliable releases.&lt;/p&gt;</description></item><item><title>CI/CD for Enterprise Angular Applications</title><link>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/ci-cd-enterprise-angular/</link><pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/ci-cd-enterprise-angular/</guid><description>&lt;h2 id="introduction-to-cicd-for-enterprise-angular"&gt;Introduction to CI/CD for Enterprise Angular&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 13! In the previous chapters, we&amp;rsquo;ve explored how to architect robust, performant, and maintainable Angular applications, from choosing rendering strategies to designing scalable routing and state management. Now, it&amp;rsquo;s time to talk about how we actually &lt;em&gt;deliver&lt;/em&gt; these amazing applications to our users consistently, reliably, and efficiently. This is where Continuous Integration and Continuous Delivery/Deployment (CI/CD) come into play.&lt;/p&gt;
&lt;p&gt;For enterprise-level Angular applications, manual deployment processes are not just slow; they&amp;rsquo;re prone to human error, lead to inconsistent environments, and can be a major bottleneck for innovation. Imagine trying to coordinate releases for a microfrontend portal with dozens of teams! CI/CD automates the entire software delivery lifecycle, from code commit to production deployment, ensuring that your users always get the latest, highest-quality features as quickly as possible.&lt;/p&gt;</description></item><item><title>Chapter 13: CI/CD Pipeline with GitHub Actions &amp;amp; AWS ECR</title><link>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/13-ci-cd-ecr/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/13-ci-cd-ecr/</guid><description>&lt;h2 id="chapter-13-cicd-pipeline-with-github-actions--aws-ecr"&gt;Chapter 13: CI/CD Pipeline with GitHub Actions &amp;amp; AWS ECR&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 13! So far, we&amp;rsquo;ve meticulously built a robust, production-ready Node.js application, complete with a well-structured codebase, comprehensive testing, secure authentication, and a Dockerized environment. In the previous chapter, we finalized our Docker setup, ensuring our application can be consistently built and run across different environments. Now, it&amp;rsquo;s time to automate the process of getting our code from development to a deployable artifact.&lt;/p&gt;</description></item><item><title>Chapter 13: CI/CD Basics with GitHub Actions</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-13-ci-cd-github-actions/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-13-ci-cd-github-actions/</guid><description>&lt;h2 id="introduction-automating-your-development-journey"&gt;Introduction: Automating Your Development Journey&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 13! So far, we&amp;rsquo;ve mastered Git for local version control, learned how to collaborate effectively with GitHub, navigated complex branching strategies, and resolved tricky merge conflicts. You&amp;rsquo;re becoming a Git and GitHub pro! But what if we could make our development process even smoother, faster, and more reliable?&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s where &lt;strong&gt;CI/CD&lt;/strong&gt; comes in. CI/CD stands for Continuous Integration and Continuous Delivery (or Continuous Deployment), and it&amp;rsquo;s a set of practices that automate much of the software development lifecycle. Imagine pushing your code, and automatically, it&amp;rsquo;s tested, checked for errors, and even deployed without you lifting another finger. Sounds magical, right?&lt;/p&gt;</description></item><item><title>CI/CD for Databricks Pipelines with Databricks Asset Bundles</title><link>https://ai-blog.noorshomelab.dev/realtime-supply-chain-intelligence-2/14-ci-cd-databricks-bundles/</link><pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/realtime-supply-chain-intelligence-2/14-ci-cd-databricks-bundles/</guid><description>&lt;h2 id="chapter-14-cicd-for-databricks-pipelines-with-databricks-asset-bundles"&gt;Chapter 14: CI/CD for Databricks Pipelines with Databricks Asset Bundles&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;In previous chapters, we meticulously crafted robust data pipelines using Databricks Delta Live Tables (DLT) for real-time ingestion, Spark Structured Streaming for logistics cost monitoring, and various Spark jobs for tariff analysis and anomaly detection. We&amp;rsquo;ve built the individual components, but deploying and managing these complex pipelines across different environments (development, staging, production) can quickly become a significant challenge without proper automation. This is where Continuous Integration/Continuous Deployment (CI/CD) comes into play, ensuring that our code changes are consistently tested, validated, and deployed.&lt;/p&gt;</description></item><item><title>CI/CD for Databricks Pipelines with Databricks Asset Bundles</title><link>https://ai-blog.noorshomelab.dev/realtime-supply-chain-intelligence/14-ci-cd-databricks-bundles/</link><pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/realtime-supply-chain-intelligence/14-ci-cd-databricks-bundles/</guid><description>&lt;h2 id="chapter-14-cicd-for-databricks-pipelines-with-databricks-asset-bundles"&gt;Chapter 14: CI/CD for Databricks Pipelines with Databricks Asset Bundles&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;In previous chapters, we meticulously crafted robust data pipelines using Databricks Delta Live Tables (DLT) for real-time ingestion, Spark Structured Streaming for logistics cost monitoring, and various Spark jobs for tariff analysis and anomaly detection. We&amp;rsquo;ve built the individual components, but deploying and managing these complex pipelines across different environments (development, staging, production) can quickly become a significant challenge without proper automation. This is where Continuous Integration/Continuous Deployment (CI/CD) comes into play, ensuring that our code changes are consistently tested, validated, and deployed.&lt;/p&gt;</description></item><item><title>Chapter 18: Setting Up CI/CD with GitHub Actions</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch18-github-actions-cicd/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch18-github-actions-cicd/</guid><description>&lt;h2 id="chapter-18-setting-up-cicd-with-github-actions"&gt;Chapter 18: Setting Up CI/CD with GitHub Actions&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 18 of our comprehensive Java project guide! In this chapter, we&amp;rsquo;ll take a significant leap towards professional software development by implementing Continuous Integration/Continuous Deployment (CI/CD) for our &amp;ldquo;Basic To-Do List Application&amp;rdquo; using GitHub Actions. CI/CD is a set of practices that enable development teams to deliver code changes more frequently and reliably by automating the build, test, and deployment processes.&lt;/p&gt;</description></item><item><title>Chapter 24: CI/CD Readiness &amp;amp; Deployment Strategies</title><link>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-24-ci-cd-deployment-strategies/</link><pubDate>Sat, 31 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-24-ci-cd-deployment-strategies/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 24! Up until now, we&amp;rsquo;ve focused heavily on building robust, performant, and maintainable React applications. But what happens after you&amp;rsquo;ve written all that beautiful code? How do you get it from your local machine out into the world for users to enjoy? That&amp;rsquo;s precisely what this chapter is all about: &lt;strong&gt;CI/CD Readiness and Deployment Strategies&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In the professional world, manually building and deploying your application every time you make a change is not only tedious but also prone to errors. This is where Continuous Integration (CI) and Continuous Deployment (CD) come to the rescue! We&amp;rsquo;ll explore how to automate these processes, making your development workflow smoother, faster, and more reliable. You&amp;rsquo;ll learn the essentials of preparing your React app for a production environment, understand different deployment options, and set up a basic CI/CD pipeline using modern tools.&lt;/p&gt;</description></item><item><title>Stop GitHub Bot Spam with Git --author</title><link>https://ai-blog.noorshomelab.dev/tutorials/stop-github-bot-spam-git-author/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/tutorials/stop-github-bot-spam-git-author/</guid><description>&lt;p&gt;&lt;strong&gt;What you&amp;rsquo;ll build:&lt;/strong&gt; You will learn to configure Git and implement CI/CD validation to prevent AI bot spam in GitHub repositories by enforcing correct commit author information.
&lt;strong&gt;Time needed:&lt;/strong&gt; ~60 minutes
&lt;strong&gt;Prerequisites:&lt;/strong&gt; Git installed, Basic Git CLI knowledge, GitHub account, Familiarity with CI/CD concepts (e.g., GitHub Actions)
&lt;strong&gt;Version used:&lt;/strong&gt; unknown&lt;/p&gt;
&lt;h3 id="understanding-the-ai-bot-spam-problem"&gt;Understanding the AI Bot Spam Problem&lt;/h3&gt;
&lt;p&gt;Maintaining a healthy open-source project or even a private team repository on GitHub can be challenging. In recent times, a new breed of problem has emerged: AI bot spam. These bots often generate low-quality, irrelevant, or even malicious content, disguised as legitimate contributions. They might open numerous issues, submit nonsensical pull requests, or push commits with generic or fake author information.&lt;/p&gt;</description></item></channel></rss>