GitHub Actions in Action (MEAP - Manning Early Access Program) (Michael Kaufmann, Rob Bos, Marcel de Vries)（Z-Library）

【One-Line Pitch】 A hands-on guide to automating software delivery with GitHub Actions, taking you from your first workflow to self-hosted runners and secure, production-grade pipelines. Best for developers, DevOps engineers, and platform teams who already use GitHub and want to replace or augment their CI/CD tooling. 【Book Arc】 - **Opening (~0%–10%)**: Frames GitHub as a full DevOps platform and GitHub Actions as its automation engine; covers the ecosystem, key terminology, hosting options, and pricing so you understand what you are buying into before writing any YAML. - **Early (~10%–32%)**: Gets you building immediately — creating a first workflow in the web editor, pulling actions from the marketplace, reading live logs, then learning YAML syntax, triggers, jobs, steps, shells, and reusable actions. - **Middle (~32%–50%)**: Deepens workflow authoring with expressions, contexts, workflow commands, environment files, and job summaries — the tools that let workflows react to events and communicate results back to developers. - **Late (~50%–70%)**: Moves into operational concerns: managing secrets and variables, authoring workflows safely in branches or forks, and understanding how runners execute jobs (hosted vs. self-hosted). - **Ending (~70%–100%)**: Covers self-hosted runners and the security measures required when hosting your own infrastructure, plus the runtime behavior of parallel and chained jobs. (Excerpts do not cover the final chapters in detail.) 【Key Takeaways】 - **GitHub is more than Git hosting** (Opening): it has grown into a six-category DevOps platform — collaborative coding, planning, CI/CD, developer productivity, client apps, and security — with Actions as the automation layer tying it together. - **Actions is broader than CI/CD** (Opening): with 18,000+ marketplace actions, it can automate issue triage, documentation generation, and other tasks, not just build and deploy. - **Pricing awareness matters early** (Early): public repos get free hosted-runner minutes; private repos have limited free minutes and storage, and default spending limits of $0 can silently block extra usage — use public repos for experimentation. - **Triggers are the highest-leverage design decision** (Early): choosing and configuring the right triggers (push, pull_request, workflow_dispatch, etc.) reduces the need for complex workflow logic later. - **Jobs run in parallel by default** (Early): the `needs` keyword chains jobs into sequences and enables fan-out/fan-in patterns; jobs are a YAML map, not a list. - **Expressions and workflow commands are the control plane** (Middle): functions like `startsWith`, `format`, and `join`, plus `::error::`-style commands and environment files, let steps communicate with the runner and surface results as annotations and job summaries. - **Authoring workflows without disrupting the team** (Middle): write in branches or forks when webhook triggers are involved, since some triggers only behave correctly from the main branch. - **Self-hosted runners shift cost and responsibility** (Late): they eliminate per-minute charges but require you to own the security measures — the book treats runner security as a first-class topic. 【Reading Tips】 - Skim Chapter 1 if you already know GitHub; slow down on the pricing and hosting sections since they affect real budget decisions. - Treat the hands-on first-workflow chapter as a lab: actually create the workflow, run it, and inspect the live log and job details rather than reading passively. - Deep-read the YAML, triggers, and expressions material — this is the syntax you will use daily, and the book explicitly builds on it in later chapters. - When you reach runners and self-hosted runners, read with your own infrastructure in mind; the security guidance is the part most likely to prevent a production incident. - Keep the companion repositories (GitHubActionsInAction organization) open alongside the text for copy-pasteable examples. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (introduction through runners and self-hosted runners); later chapters on advanced runtime, security hardening, and real-world pipeline patterns are only partially represented. Specific chapter titles and figures beyond those referenced in the excerpts are not covered.