Monitor Workflow Runs

Warestack monitors every GitHub Actions workflow run in real time, linking it with related pull requests, commits, and deployments.
It also enriches this data with metadata coming from your custom checks. Read more ↗.

How it works

1. Collects signals from every workflow execution — build, test, and deployment steps — in real time.
2. Correlates context from tools like Slack and Linear to tie CI/CD runs with PR discussions or issue updates.
3. Applies checks for failed jobs, skipped tests, or performance regressions across runs.
4. Surfaces insights in the Warestack dashboard and API for visibility, auditing, and automated alerts.

{
"type": "GitHub Workflow Run",
"title": "Manual Deployment (api-staging.warestack.com)",
"metadata": {
  "workflow_file": "manual-deploy.yml",
  "repository": "core-api",
  "status": "Success",
  "triggered_by": "dkargatzis",
  "updated": "13 hours ago",
  "labels": ["Admins", "Backend"]
},
"overview": [
  "Workflow run triggered by dkargatzis 13 hours ago",
  "Completed successfully with all checks passed"
],
"associations": [
  {
    "type": "Pull Request",
    "description": "Add GitHub API rate limiting and NUL byte fix",
    "status": "closed",
    "updated": "13h ago"
  },
  {
    "type": "Issue",
    "description": "Investigate NULL byte errors in staging",
    "status": "closed",
    "updated": "2d ago"
  }
],
"associated_linear_issue": {
  "key": "LIN-431",
  "status": "Scope verified",
  "note": "Rollout to staging approved"
},
"slack_summary": {
  "channel": "#backend",
  "message": "Successful run confirmed. Logs validated for staging. Next step: enable rate-limit tests in CI."
},
"summary": "This workflow run builds, tests, and deploys the latest commit to staging, maintaining sync with linked issues and PRs."
}

Suggested checks

We recommend you activate the basic checks.

• flag failed workflows

  Detects any workflow run that failed and reports it in real time.

• alert when workflow is rerun more than X times

  Helps identify unstable or flaky pipelines that frequently fail and retry.

• notify when test coverage drops below threshold

  Tracks code quality drift by comparing coverage metrics across runs.

• block merge if required workflow not completed

  Ensures that critical pipelines finish successfully before allowing merges.