ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #githubactions
Learn how to define a GitHub Actions reusable workflow, call it with inputs and secrets, and avoid common pitfalls such as missing triggers, wrong version references, and double checkout.
Set up a GitHub Actions matrix strategy to run your Node.js test suite across multiple runtime versions in parallel, with per-version results, caching, and targeted reruns.
GitHub Actions can mint short-lived OIDC tokens that cloud providers exchange for temporary credentials — no stored secrets. The security lives in the cloud-side trust condition, not the token.
Reusable workflows let you extract common CI logic into a single file, share it across repos, and keep everything in sync. Learn how to define inputs/outputs, pass secrets safely, and version your shared workflows for reliable, maintainable pipelines.
Duplicate CI pipelines cost time. Reusable workflows let you centralize build, test, and release logic in one repo, passing inputs, outputs, and secrets to callers. This article gives a concrete example, discusses versioning trade‑offs, and offers a checklist for safe adoption.
Reusable workflows let you extract CI/CD logic into a single file and call it from many places. Learn the exact syntax, how to pass inputs and capture outputs, and the subtle gotchas that can break caching or leak secrets.
A step‑by‑step diagnostic guide for the most common reasons a GitHub Actions caller workflow cannot invoke a reusable workflow, with a symptom‑to‑cause table, ordered verification commands, and concrete YAML examples.
A step‑by‑step guide to identify why a self‑hosted runner shows as offline and how to restore it.
Duplicate CI pipelines across repos? Use GitHub Actions reusable workflows to centralize logic, reduce drift, and simplify maintenance. Learn how to set up, call, and version a reusable workflow with a concrete example and trade‑offs.
nodejs