Monitor Pull Requests

Warestack monitors every pull request in real time, linking it with related commits, reviews, and workflows.
It also enriches this data with metadata coming from your custom checks. Read more ↗.

How it works

Collects signals to detect every update (commits, comments, reviewers, CI checks) in real time.
Correlates discussions from Slack and PM tools like Linear or Jira.
Runs checks against your defined rules (e.g., review required, diff scope match, branch protection).
Reports insights in the Warestack dashboard or via API.

Example of a Warestack Pull Request

This is an example of a typical GitHub pull request enriched with metadata, associated workflows, and automated checks powered by Warestack. In this case, active checks detected missing reviews and confirmed that all CI runs were completed before merge.

GitHub Pull Request Information

fix: Add GitHub API rate limiting and PostgreSQL NULL byte sanitization

Author

Stelios

Repository

core-api

Status

Closed

Updated

13 hours ago

Overview

Mary and Dimitris assigned as reviewers.
Merged from fix/dev-579-fix-github-api-rate-limiting-and-postgresql-null-byte-errors into main.
Adds rate-limit handling for GitHub API and sanitizes NULL byte issues for PostgreSQL.

Checks

Code review required — no approval found for this pull request.
All CI checks passed successfully before merge.

Associated Workflow Runs

build-and-test.yml — completed successfully (run #231)
manual-deploy.yml — completed 16 hours ago

Associated Linear Issue

LIN-431 — PR diff is aligned with the scope and acceptance criteria of the issue.

Stats

Reviewers

Commits

Files changed

Reviews

Approvals

Slack Summary

#backend discussed failed review automation and CI passes.
Confirmed safe to merge; validation checks to be enforced in next release.

This example shows how Warestack enriches a GitHub issue with all related signals in a single source of truth. It helps teams understand issue progress instantly, reduces manual tracking, and ensures every update aligns with development and review standards.

View JSON representation

{
"type": "GitHub Issue",
"title": "feat(manage-checks): enable inline edit for checks",
"metadata": {
  "author": "steliosot",
  "repository": "core-api",
  "status": "Open",
  "updated": "1 day ago"
},
"description": "Enable inline editing for checks from the Manage Checks page. Use a small modal to update description, condition, or severity.",
"checks": [
  {
    "rule": "Label required",
    "details": "Add one like 'enhancement' or 'help wanted'."
  },
  {
    "rule": "Stale issue detection",
    "details": "Issue is stale for more than 5 days."
  }
],
"associated_pull_request": {
  "title": "feat(checks): add inline edit modal and PATCH endpoint"
},
"associated_workflow_run": {
  "name": "build-and-test.yml",
  "status": "passed successfully",
  "run_id": 154
},
"slack_summary": {
  "channel": "#dev-core",
  "message": "Team confirmed inline edit feature improves setup flow. Implementation scheduled for next sprint."
},
"summary": "This Warestack issue shows how all related activities—PRs, workflows, and discussions—are unified into a single view. Teams gain complete traceability and reduce manual coordination."
}

Suggested checks

💡 TIP — Activate Warestack’s standard checks.

flag PRs merged without review
Ensures every pull request receives at least one approval before merging.
alert when PR diff is not aligned with issue scope
Detects pull requests that modify unrelated files or exceed their intended scope.
notify when PR is stale for more than X days
Highlights PRs that remain open or idle for too long without updates.
block merge if workflow or tests failed
Prevents merging changes when required CI/CD checks or tests are still failing.