{"id":24625,"date":"2014-09-07T22:52:05","date_gmt":"2014-09-08T03:52:05","guid":{"rendered":"https:\/\/wordpress-1325650-4848760.cloudwaysapps.com\/?p=24625"},"modified":"2025-05-15T11:26:29","modified_gmt":"2025-05-15T15:26:29","slug":"github-actions-tutorial","status":"publish","type":"post","link":"https:\/\/codesamplez.com\/devops\/github-actions-tutorial","title":{"rendered":"GitHub Actions Tutorial: Automating Your Deployment Workflow"},"content":{"rendered":"\n

Automation With Github Actions automation has completely transformed how I handle deployments. Back in the old days (which wasn’t actually that long ago), we relied on clunky webhooks on github and custom scripts to get our code from repository to production. While those methods worked, but they were absolutely painful to maintain.<\/p>\n\n\n\n

In this Github Actions tutorial, I’m going to show you EXACTLY how to create powerful, flexible deployment workflows that will save you countless hours of manual work. Trust me, once you start automating your deployments, you’ll never want to go back to the old ways.<\/p>\n\n\n\n

What Are GitHub Actions?<\/h2>\n\n\n\n

GitHub Actions is a CI\/CD (Continuous Integration\/Continuous Deployment) platform built directly into GitHub. It lets you automate your build, test, and deployment pipeline without needing to set up any external systems.<\/p>\n\n\n\n

Unlike the old webhook approach that required maintaining separate build scripts and servers, GitHub Actions handles everything within the GitHub ecosystem. This means faster setup, better integration, and less headache.<\/p>\n\n\n\n

The best part? Every GitHub repository comes with free build minutes each month – 2,000 minutes for public repositories and 3,000 minutes for private repositories on the free plan. That’s seriously generous, especially for smaller projects.<\/p>\n\n\n\n

Tip \ud83d\udca1: level up your productivity with our git commands cheat sheet<\/a>!<\/em><\/p>\n\n\n\n

Why You Need GitHub Actions<\/h2>\n\n\n\n

Before diving into the how-to, let’s talk about why you absolutely need to be using GitHub Actions:<\/p>\n\n\n\n

    \n
  1. Save tremendous time<\/strong> by automating repetitive deployment tasks<\/li>\n\n\n\n
  2. Reduce human errors<\/strong> that inevitably happen during manual deployments<\/li>\n\n\n\n
  3. Maintain consistent environments<\/strong> across development, staging, and production<\/li>\n\n\n\n
  4. Get instant feedback<\/strong> when something breaks<\/li>\n\n\n\n
  5. Create robust testing workflows<\/strong> that run automatically<\/li>\n\n\n\n
  6. Scale easily<\/strong> as your project grows<\/li>\n<\/ol>\n\n\n\n

    Honestly, the benefits are so substantial that I can’t imagine working without automated workflows anymore.<\/p>\n\n\n\n

    Getting Started with GitHub Actions<\/h2>\n\n\n\n

    Setting up your first GitHub Action workflow is incredibly straightforward. Let’s break it down step by step:<\/p>\n\n\n\n

    Step 1: Create Your Workflow File<\/h3>\n\n\n\n

    GitHub Actions workflows are defined in YAML files stored in the .github\/workflows<\/code> directory of your repository. Let’s create a simple deployment workflow:<\/p>\n\n\n\n

      \n
    1. In your repository, create the directory .github\/workflows<\/code> if it doesn’t already exist<\/li>\n\n\n\n
    2. Create a new file called deploy.yml<\/code> in that directory<\/li>\n<\/ol>\n\n\n\n

      Here’s a basic workflow to get you started:<\/p>\n\n\n

      name: Deploy Application\n\non:\n  push:\n    branches: [ main ]\n  workflow_dispatch:  # Allows manual triggering<\/span>\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Checkout code\n        uses: actions\/checkout@v3\n      \n      - name: Setup Node.js\n        uses: actions\/setup-node@v3\n        with:\n          node-version: '16'<\/span>\n      \n      - name: Install dependencies\n        run: npm install\n      \n      - name: Build application\n        run: npm run build\n      \n      - name: Deploy to server\n        uses: easingthemes\/ssh-deploy@v4.1<\/span>.8<\/span>\n        with:\n          SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}\n          REMOTE_HOST: ${{ secrets.REMOTE_HOST }}\n          REMOTE_USER: ${{ secrets.REMOTE_USER }}\n          SOURCE: \"dist\/\"<\/span>\n          TARGET: \"\/var\/www\/html\/\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This workflow will trigger whenever someone pushes to the main branch, checkout the code, set up Node.js, install dependencies, build the application, and then deploy it to your server using SSH.<\/p>\n\n\n\n
      Step 2: Set Up Secrets<\/h3>\n\n\n\n
      For the deployment step, we need to securely store our SSH credentials. GitHub provides a secure way to store sensitive information using Secrets:<\/p>\n\n\n\n
        \n
      1. Go to your repository settings<\/li>\n\n\n\n
      2. Click on “Secrets and variables” and then “Actions”<\/li>\n\n\n\n
      3. Click “New repository secret”<\/li>\n\n\n\n
      4. Add secrets for SSH_PRIVATE_KEY<\/code>, REMOTE_HOST<\/code>, and REMOTE_USER<\/code><\/li>\n<\/ol>\n\n\n\n
        These secrets are encrypted and only exposed to the GitHub Actions workflow during run time. They’ll never be visible in logs or to people who don’t have admin access to your repository.<\/p>\n\n\n\n
        Step 3: Push Your Changes<\/h3>\n\n\n\n
        Commit your workflow file and push it to your repository. This will automatically trigger the workflow if you’re pushing to the main branch.<\/p>\n\n\n\n
        Understanding Workflow Syntax<\/h2>\n\n\n\n
        Let’s break down the key components of a GitHub Actions workflow:<\/p>\n\n\n\n
        Triggers<\/h3>\n\n\n\n
        The on<\/code> section defines when your workflow should run:<\/p>\n\n\n
        on:\n  push:\n    branches: [ main, develop ]\n  pull_request:\n    branches: [ main ]\n  schedule:\n    - cron: '0 0 * * *'<\/span>  # Run daily at midnight<\/span>\n  workflow_dispatch:     # Manual trigger<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        You can trigger workflows on pushes, pull requests, on a schedule using cron syntax, or manually using the workflow_dispatch<\/code> event.<\/p>\n\n\n\n
        Jobs<\/h3>\n\n\n\n
        Workflows are made up of one or more jobs that can run in parallel or sequentially:<\/p>\n\n\n
        jobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      # Test steps here<\/span>\n  \n  build:\n    needs: test  # This job will only run after 'test' completes<\/span>\n    runs-on: windows-latest\n    steps:\n      # Build steps here<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        The needs<\/code> keyword creates dependencies between jobs, ensuring they run in the right order.<\/p>\n\n\n\n
        Runners<\/h3>\n\n\n\n
        The runs-on<\/code> property specifies the type of machine to run the job on. GitHub provides runners for Linux, Windows, and macOS:<\/p>\n\n\n\n