Introduction to GitHub Actions

What is GitHub Actions?

GitHub Actions is an automation platform provided by GitHub that enables Continuous Integration (CI) and Continuous Deployment (CD) directly within your GitHub repository. It automates workflows, such as building, testing, and deploying applications whenever changes occur in the repository.

With GitHub Actions, developers can:
✔ Automate software development workflows like CI/CD pipelines.
✔ Run tests automatically on every commit and pull request.
✔ Deploy applications to cloud platforms, servers, or production environments.
✔ Integrate third-party services using prebuilt marketplace actions.

This article covers everything about GitHub Actions, including:

• Environment variables, caching, and marketplace actions.
• Deploying with GitHub Actions (Elastic Beanstalk, Chrome Extensions, etc.).
• Using SSH keys for secure automation.

Table of Contents

1. GitHub Actions Basics
2. How GitHub Actions Work
3. Key Components of GitHub Actions
4. GitHub Actions Environment Variables
5. Using GitHub Actions Cache
6. Deploying with GitHub Actions
7. GitHub Actions Marketplace
8. Using SSH Keys with GitHub Actions
9. GitHub Actions Matrix Builds
10. Best Practices for GitHub Actions
11. Conclusion

🔗 Official Documentation:

• GitHub Actions Docs
• GitHub Actions Marketplace

1. GitHub Actions Basics

GitHub Actions allows users to automate workflows by triggering actions based on events in a repository. This automation eliminates manual steps for testing, deployment, and environment setup.

Common GitHub Actions Use Cases include:

• Running unit tests before merging a pull request.
• Deploying applications automatically when code is pushed.
• Automating issue labeling and triaging.

2. How GitHub Actions Work

GitHub Actions operate based on workflows that define what should happen when a certain event occurs.

Example: Simple GitHub Actions Workflow

name: My GitHub Actions Workflow

on: [push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Repository
        uses: actions/checkout@v3

      - name: Run a script
        run: echo "Hello, GitHub Actions!"

🔹 This workflow runs automatically when a push or pull request is made.
🔹 It checks out the repository and executes a script.

3. Key Components of GitHub Actions

4. GitHub Actions Environment Variables

GitHub Actions provides built-in environment variables for customizing workflows.

Example: Using Environment Variables

jobs:
  build:
    runs-on: ubuntu-latest
    env:
      APP_ENV: production
    steps:
      - name: Display Environment Variables
        run: echo "Environment is $APP_ENV"

🔹 Built-in Variables: GITHUB_REPOSITORY, GITHUB_ACTOR, GITHUB_RUN_ID
🔹 Custom Variables: You can define and use your own environment variables.

For more details, refer to GitHub Actions Environment Variables.

5. Using GitHub Actions Cache

Caching dependencies speeds up workflow execution.

Example: Caching npm Dependencies

steps:
  - uses: actions/cache@v3
    with:
      path: ~/.npm
      key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
      restore-keys: |
        ${{ runner.os }}-npm-

🔹 Reduces build times by avoiding redundant installations.

More details: GitHub Actions Cache.

6. Deploying with GitHub Actions

Deploying to Elastic Beanstalk

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Deploy to AWS Elastic Beanstalk
        uses: einaregilsson/beanstalk-deploy@v20
        with:
          aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws_secret_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          application_name: MyApp
          environment_name: MyApp-env

Deploying a Chrome Extension

jobs:
  deploy:
    steps:
      - name: Upload to Chrome Web Store
        uses: trmcnvn/chrome-addon@v2
        with:
          extension-id: abc123
          client-id: ${{ secrets.CHROME_CLIENT_ID }}
          client-secret: ${{ secrets.CHROME_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CHROME_REFRESH_TOKEN }}

7. Introduction to GitHub Actions Marketplace

🔗 GitHub Actions Marketplace provides thousands of prebuilt automation scripts, including:
✔ Checkout repository (actions/checkout)
✔ Setup Node.js (actions/setup-node)
✔ Deploy AWS Lambda (aws-actions/aws-lambda-deploy)

Use these actions to save time and simplify workflows.

8. Using SSH Keys with GitHub Actions

🔐 Secure deployments by using SSH keys to authenticate with GitHub.

Example: SSH Key Authentication

steps:
  - name: Setup SSH Key
    run: |
      echo "${{ secrets.SSH_PRIVATE_KEY }}" > ~/.ssh/id_rsa
      chmod 600 ~/.ssh/id_rsa

More details: GitHub Actions SSH Key Integration.

9. GitHub Actions Matrix Builds

Matrix builds allow you to test on multiple OS versions simultaneously.

Example: Running Tests on Different OS Versions

jobs:
  test:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest, macos-latest]
    steps:
      - run: echo "Testing on ${{ matrix.os }}"

🔹 Useful for cross-platform testing.

10. Best Practices for GitHub Actions

✔ Use caching to speed up builds.
✔ Encrypt secrets (e.g., API keys) using GitHub Secrets.
✔ Use reusable workflows for consistency.
✔ Leverage the Marketplace for prebuilt actions.

11. Conclusion

GitHub Actions is a powerful automation tool that integrates CI/CD seamlessly into GitHub repositories. It supports environment variables, caching, SSH authentication, and deployment to cloud platforms.

🚀 Next Steps:

• Explore GitHub Actions Marketplace.
• Implement Matrix Builds to run tests across multiple environments.
• Automate Elastic Beanstalk or Chrome Extension deployments.

Learn more about how to use github actions for ci/cd​