Blog

Guides and deep dives on GitHub Actions, CI/CD and developer workflows.

Squidly blog cover: Re-run only the failed job in GitHub Actions. Next to it, one test job re-running while the successful jobs are kept.

4 min read

Re-run Only the Failed Job in GitHub Actions

Re-run only the failed GitHub Actions job, read its logs first, and see when a single run is no longer enough across several repositories.

  • github-actions
  • ci-cd
  • debugging
Squidly blog cover: Do you need a GitHub Actions dashboard? Next to it, when the native Actions tab is enough and when a central dashboard helps.

4 min read

Do You Need a GitHub Actions Dashboard?

Is the native Actions tab enough, or do you need a GitHub Actions dashboard? A decision guide based on how many repositories you follow.

  • github-actions
  • comparison
  • dashboard
  • ci
Squidly blog cover: Monitor GitHub Actions across multiple repositories. Next to it, runs from five repositories in three organizations, one build failed.

5 min read

Monitor GitHub Actions Across Multiple Repositories

Need to monitor GitHub Actions across multiple repositories? Compare per-repo Actions tabs, notifications and scripts, and see where a central view helps.

  • github-actions
  • monitoring
  • multi-repo
  • ci
Squidly blog cover: Debug a failing GitHub Actions workflow in 6 steps. Next to it, a run whose Run tests step failed with exit code 1 and Deploy was skipped.

4 min read

Debug a Failing GitHub Actions Workflow in 6 Steps

GitHub Actions workflow failing? Follow a 6-step method to read the logs, isolate the cause and fix it fast, across one or many repositories.

  • github-actions
  • ci
  • debug
  • workflows