ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Stop storing long-lived API tokens in your CI/CD secrets. Learn how to use PyPI Trusted Publishers and OIDC to secure your package deployments via GitHub Actions.
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 concise, secure GitHub Actions pipeline using separate build, test, and deploy workflows, self‑hosted runners, and GitHub Secrets to enforce ordering, isolate secrets, and monitor runner health.
A step‑by‑step guide to identify why a self‑hosted runner shows as offline and how to restore it.
Learn how to use GitHub Actions' cache action to reuse npm, pip, or Maven dependencies across workflow runs, reducing CI time and staying within storage limits.
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.
Stop duplicating CI/CD YAML across your repositories. Learn how to use GitHub Reusable Workflows to centralize pipeline logic, manage versioning, and eliminate pipeline drift.
githubactions
pypi
github
nodejs