<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sunny kumar Sinha</title>
    <description>The latest articles on DEV Community by Sunny kumar Sinha (@sunny_sinha).</description>
    <link>https://dev.to/sunny_sinha</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3042441%2Fd34c84aa-ab30-4c4b-bd2b-92d6def49a1b.png</url>
      <title>DEV Community: Sunny kumar Sinha</title>
      <link>https://dev.to/sunny_sinha</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sunny_sinha"/>
    <language>en</language>
    <item>
      <title>Github Actions :- CI &amp;&amp; CD</title>
      <dc:creator>Sunny kumar Sinha</dc:creator>
      <pubDate>Sat, 18 Apr 2026 07:36:46 +0000</pubDate>
      <link>https://dev.to/sunny_sinha/github-actions-ci-cd-46j6</link>
      <guid>https://dev.to/sunny_sinha/github-actions-ci-cd-46j6</guid>
      <description>&lt;p&gt;What is Github Actions ?&lt;br&gt;
GitHub Actions is a CI/CD tool that automates workflows like building, testing, and deploying code directly from a GitHub repository based on events such as pushes or pull requests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;⚙️ Continuous Integration (CI)&lt;/strong&gt;&lt;br&gt;
Continuous Integration (CI) automatically builds and tests your code whenever you push changes to a repository, helping catch errors early.&lt;br&gt;
👉 Example/Use Case: When you push code to GitHub, tests run automatically to ensure your new feature doesn’t break existing functionality.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🚀 Continuous Deployment (CD)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Continuous Deployment (CD) automatically deploys your code to production after it passes all tests and checks.&lt;br&gt;
👉 Example/Use Case: After your code passes tests, it is automatically deployed to a live server like Vercel or Render without manual steps.&lt;/p&gt;



&lt;p&gt;🏗️ GitHub Actions Architecture (Simple Explanation)&lt;/p&gt;

&lt;p&gt;You can explain it like a flow 👇&lt;/p&gt;

&lt;p&gt;GitHub Actions works on an event-driven architecture where a trigger starts a workflow, which runs jobs made up of steps on a runner.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Overall workflow&lt;/strong&gt;&lt;br&gt;
&lt;em&gt;Event → Workflow → Jobs → Steps → Runner&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;⚙️ 1. Event (Trigger)&lt;/p&gt;

&lt;p&gt;This is what starts everything.&lt;/p&gt;

&lt;p&gt;Examples:&lt;/p&gt;

&lt;p&gt;push&lt;br&gt;
pull_request&lt;br&gt;
schedule&lt;/p&gt;

&lt;p&gt;👉 Example:&lt;/p&gt;

&lt;p&gt;When you push code to GitHub, it triggers the workflow.&lt;/p&gt;

&lt;p&gt;📄 2. Workflow&lt;br&gt;
A YAML file inside .github/workflows/&lt;br&gt;
Defines what should happen&lt;/p&gt;

&lt;p&gt;👉 It contains:&lt;/p&gt;

&lt;p&gt;Events&lt;br&gt;
Jobs&lt;br&gt;
🧩 3. Jobs&lt;br&gt;
A workflow can have multiple jobs&lt;br&gt;
Each job runs independently&lt;/p&gt;

&lt;p&gt;👉 Example:&lt;/p&gt;

&lt;p&gt;Job 1 → Install dependencies&lt;br&gt;
Job 2 → Run tests&lt;br&gt;
🔹 4. Steps&lt;br&gt;
Each job is made of steps&lt;br&gt;
Steps are individual tasks&lt;/p&gt;

&lt;p&gt;👉 Example:&lt;/p&gt;

&lt;p&gt;Checkout code&lt;br&gt;
Install Node.js&lt;br&gt;
Run tests&lt;br&gt;
🖥️ 5. Runner&lt;br&gt;
A machine that executes the job&lt;/p&gt;

&lt;p&gt;Types:&lt;/p&gt;

&lt;p&gt;Ubuntu (most common)&lt;br&gt;
Windows&lt;br&gt;
macOS&lt;/p&gt;



&lt;p&gt;&lt;strong&gt;💻 Practical Example: Running Tests with GitHub Actions&lt;/strong&gt;&lt;br&gt;
To understand GitHub Actions better, let’s look at a simple real example.&lt;/p&gt;

&lt;p&gt;In this project, I created a basic Python function that adds two numbers and wrote test cases to verify its correctness.&lt;br&gt;
&lt;em&gt;Here is addtion.py(python) file&lt;/em&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;b&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;a&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;b&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;test_add&lt;/span&gt;&lt;span class="p"&gt;():&lt;/span&gt;
    &lt;span class="k"&gt;assert&lt;/span&gt; &lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;
    &lt;span class="k"&gt;assert&lt;/span&gt; &lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;u&gt;Here is the GitHub Actions workflow file: &lt;/u&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;My First GitHub Actions&lt;/span&gt;

&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;push&lt;/span&gt;&lt;span class="pi"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;build&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;

    &lt;span class="na"&gt;strategy&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="na"&gt;matrix&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
        &lt;span class="na"&gt;python-version&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;3.8&lt;/span&gt;&lt;span class="pi"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;3.9&lt;/span&gt;&lt;span class="pi"&gt;]&lt;/span&gt;

    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@v3&lt;/span&gt;

    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Set up Python&lt;/span&gt;
      &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/setup-python@v2&lt;/span&gt;
      &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
        &lt;span class="na"&gt;python-version&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;${{ matrix.python-version }}&lt;/span&gt;

    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Install dependencies&lt;/span&gt;
      &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;|&lt;/span&gt;
        &lt;span class="s"&gt;python -m pip install --upgrade pip&lt;/span&gt;
        &lt;span class="s"&gt;pip install pytest&lt;/span&gt;

    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Run tests&lt;/span&gt;
      &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;|&lt;/span&gt;
        &lt;span class="s"&gt;cd src&lt;/span&gt;
        &lt;span class="s"&gt;python -m pytest addition.py&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;📁 Where to Place the Workflow File&lt;/p&gt;

&lt;p&gt;For GitHub Actions to work, the YAML file must be placed in this path:&lt;/p&gt;

&lt;p&gt;.github/workflows/first-actions.yaml&lt;/p&gt;

&lt;p&gt;👉 Explanation:&lt;/p&gt;

&lt;p&gt;.github/ → Special GitHub folder&lt;br&gt;
workflows/ → Stores all workflow files&lt;br&gt;
.yaml file → Your automation script&lt;/p&gt;

&lt;p&gt;⚠️ If you place the file anywhere else, GitHub Actions will NOT run.&lt;/p&gt;




&lt;p&gt;I actually implemented this in one of my projects to understand it better.&lt;br&gt;
You can take a look at the full setup here:&lt;br&gt;
👉 &lt;a href="https://github.com/Sunny-2610/github_actions" rel="noopener noreferrer"&gt;https://github.com/Sunny-2610/github_actions&lt;/a&gt;&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>cicd</category>
      <category>devops</category>
      <category>github</category>
    </item>
  </channel>
</rss>
