Continuous integration and continuous deployment (CI/CD) platform provided by GitHub for automating workflows, testing, and deployments.
Pricing: 0 USD · Updated 2026-09-03
developmentYes. GitHub Actions is free for public repositories and limited private usage; paid plans exist for larger private usage quotas.
GitHub Actions is a CI/CD platform for automating workflows, testing and deployments directly from GitHub repositories.
Git explained: what version control is, how Git stores history as content-addressed snapshots, why branches are cheap, and how Git and GitHub fit together.
Docker explained: what containers are, how Docker Engine uses Linux namespaces and cgroups, how images, Dockerfiles, and Docker Compose fit together, and how Docker compares with virtual machines.
Set up SSH key authentication for GitHub and Linux servers: generate Ed25519 keys, add to ssh-agent, copy public key, and test connection — step-by-step with open-license sources.
Set up a CI/CD pipeline with GitHub Actions: create your first workflow, configure triggers, build and test your code on runners, use actions and secrets, and deploy automatically — open-license sources.
Build a complete Node.js + Prometheus + Grafana monitoring stack: instrument Express with prom-client, scrape metrics, run Prometheus in Docker, build Grafana dashboards with PromQL, and configure alerts. Includes a working docker-compose example.
Monoliths and microservices are the two main ways to structure an application. A monolith ships as one deployable unit with a single codebase, while microservices split an app into small independent services that each own their data and scale alone. Compare the trade-offs and learn how to choose.
Environment variables are the standard way to configure a Node.js app without hardcoding values. Node reads them through process.env, you can load them from .env files with the built-in --env-file flag or the dotenv package, and secrets should stay out of your code and version control. This guide walks through each approach and when to use it.
A webhook is a user-defined HTTP callback: one service sends an HTTP request to a URL you control when an event happens. Learn how they work, how they differ from polling and regular APIs, and how to verify signatures and handle retries safely.
Compare the most common Git branching strategies — GitFlow, GitHub Flow, and trunk-based development — with concrete commands, branch structures, and a guide to choosing the right workflow for your team's release cadence and size.
CI/CD automates the path from code commit to production: continuous integration builds and tests every change, continuous delivery keeps releases ready, continuous deployment ships them automatically.
YAML (YAML Ain't Markup Language) is a human-readable data serialization format used for configuration files, CI/CD pipelines, and cross-language data exchange. This guide explains YAML syntax, key features, common tools, and security pitfalls.
Bash is the default Unix shell on most Linux distributions and on macOS. Learn how Bash scripts work: variables, parameter expansion, conditionals, loops, functions, exit codes, and best practices for reliable, safe scripts.
Unit testing is the practice of testing the smallest testable parts of a program — functions, methods, or classes — in isolation. Learn what a unit test is, the arrange-act-assert structure, test doubles and mocking, the testing pyramid, and best practices for writing good unit tests.
A canary deployment rolls out a new version to a small subset of users first, then gradually expands if metrics stay healthy. Compare canary vs rolling update vs blue-green, learn the metrics to watch, and see when this progressive-delivery pattern fits your team.