Every workflow run stays in your Actions history forever, unless you clean it up yourself. After a year or two of CI, that history turns into thousands of runs nobody will ever open again. Scrolling through them to find anything useful becomes painful. That is why I built Prune Old GitHub Actions Runs , a GitHub Action that deletes workflow runs older than a number of days you choose, on a schedul... [read more]

In this article we will learn an efficient way to delete old GitHub Actions runs. Wondering how to keep the history of Actions clean? ▶️ Org-level retention policy (does not delete the run itself) ▶️ Repo-level retention policy (does not delete the run itself) ✅ Or a more granular automated way? (deletes the run) If you use GitHub, Actions is the native way to build a CI/CD pipeline. However, if y... [read more]

CI/CD best practices ✅ Keep the pipeline fast ✅ Fail fast For example, if "integration tests" fail more often than "unit tests", run them first. ✅ Do not run everything every time Do you need to run the linter in PR? Yes Do you need to run the linter after the merge? Probably not ✅ Avoid "God" pipelines! Split the workflow when it makes sense. ✅ Do not use long-lasting credentials/tokens. If possi... [read more]