Org engineering standards live in wikis. Nothing checks pull requests against them.

Warestack checks pull requests and deployments against your organization’s delivery standards. See missing approvals, linked work items and rule findings where your team already works.

Get started

Install from GitHub Marketplace

Start with the Free plan. Choose the repositories you want to connect.

feat(reports): export deployment approvals as CSV (ENG-1012) #1182

Openamira wants to merge 4 commits into main from feat/ENG-1012-export-deployment-approvals

Some checks haven’t completed yet

1 expected, 1 in progress, 2 successful checks

1 expected check

Warestack Rules Expected — Waiting for status to be reported

Required

1 in-progress check

Run pre-commit hooks / Lint code and README files (pull_request) In progress

2 successful checks

CI / build (pull_request) Successful in 10s

CodeQL Successful in 15s

Merging is blocked

Waiting for required checks to pass.

Some checks were not successful

1 failing, 3 successful checks

1 failing check

Warestack Rules — Blocking rule evaluation incomplete

Required

3 successful checks

CI / build (pull_request) Successful in 10s

Run pre-commit hooks / Lint code and README files (pull_request) Successful in 23s

CodeQL Successful in 15s

Merging is blocked

The required Warestack Rules check has failed.

Warestack

Warestack Rules

Warestack / Warestack Rules

Failed

Blocking rule evaluation incomplete

DETAILS

1 blocking Warestack rule could not be evaluated. Warestack fails closed when a merge-blocking rule has no trusted outcome.

Unavailable blocking rules:

Follow repository instructions: No complete, validated outcome was produced for this revision.

How to unblock:

Push an update after the reported evidence issue is resolved.
Or select Re-run evaluation below to retry this exact pull-request revision.

Re-run evaluation

View more details on Warestack

Illustrative GitHub walkthrough. Sample data; merge blocking enabled.

GitHub Technology Partner

01How it works

A rule finds the problem. A chain acts on it. A report keeps the record.

Sample pull request · reporting onlyQueued

Pull request

console-web #1182

Rule

Require approvals by branch prefix

Slack

GitHub

Linear

Report

Approvals report

01Rules

Write a standard in plain English and Warestack turns it into checks you can read before turning them on. A catalog covers the common ones: linked issues, independent approvals, scope, size, tests, deploy windows.

Example rule

Pull requests that change db/migrations/ must include a Rollback section.

Enabled on orbital/control-plane. 14 pull requests checked this week, 2 flagged.

02Chains

Choose a trigger, the steps that follow and when they stop. Chains can keep a Slack card current, remind a reviewer, announce a deployment or deliver a saved report.

Example · Pull request live card

Pull request opens → live card in Slack → after 12h, remind the channel if no review was submitted.

The card stays current until merge or close. A submitted review skips the reminder.

03Reports

Ask a question in plain English and get the answer with the rows behind it. Save the result, schedule it to Slack or email, or export the CSV. Retention follows your plan or agreement. The record for the auditor, the board, or the incident review.

Example report

Which production deployments in the last 30 days had no independent approval?

3 rows · orbital/control-plane, orbital/billing-service · CSV attached

Not a code reviewerWarestack checks how a change was delivered, not what the code says. It does not review code, run your CI or orchestrate coding agents. People and agents are held to the same standards at the same point, the pull request.

02Where it shows up

It shows up where your team already works.

GitHub connects first. Add Slack, Linear or Jira to keep findings, follow-up and reports close to the work.

03Rollout

As wide as the organization. As narrow as one folder.

Every rule is enabled on a scope you choose: a team, a repository, or a path inside one. Different rules, different scopes, one organization. New repositories join their team's rules as they arrive.

teamPlatform gets independent production approval on all seven of its repositories, including the ones created next quarter.

repobilling-service alone needs a finance-eng approval on pricing changes.

pathcontrol-plane/db/migrations/ is the only place the rollback-notes rule runs. Nowhere else sees it.

Rules report first. Merge blocking is a separate switch, per repository, that stays off until you require the check in branch protection.

Independent production approvalteam · Platform

Finance approval on pricingrepo

Migration rollback notespath

orbital12 repositories · 3 teams

Platform7 repositories

control-plane

db/migrations/

collector-agent

ingest

auth-service

terraform-modules

sdk-go

cli

Product3 repositories

console-web

billing-service

mobile

Shared2 repositories · no rules

docs

design-system

Merge blockingOff · check not required0 scopes

04Evidence

The record is ready before anyone asks for it.

Ask a question in plain English. Inspect the rows behind the answer, export a CSV, or schedule delivery to Slack or email. Data retention follows your plan or agreement.

For the auditorReview the approver, checks, linked issue and deployment details available for each recorded change. Export the rows for a change-management review.

For the incident reviewWhat shipped, when, and who approved it, without reconstructing it from chat history.

Question

Answer

3 of 186 production deployments were approved by the person who requested them.

Sample production deployments without independent approval
Repository	Deploy	Approved by	Finished
control-plane	#2061	rdiaz, the requester	Sep 30
billing-service	#598	tobiaslind, the requester	Sep 24
collector-agent	#418	ipetrov, the requester	Sep 19

3 rows · sample resultDownload CSVSchedule weekly

05The pilot

Four weeks on one to three repositories.

Agree on a success measure before installation. Start in reporting mode, then decide which checks to require.

Week 1

Install and observe

The app on the pilot repositories. Rules from the catalog plus two of yours, reporting only. The baseline is recorded.

Weeks 2 to 3

Chains on

Live cards in Slack, the timeline on Linear or Jira, escalation to named owners. Rules are tuned against real pull requests.

Week 4

Review the evidence

The metric against the baseline, from the reports. Decide which rules become required checks, and on which repositories.

Free · Try Warestack on a small set of repositories.$0

Pro · A platform fee with separate allowances for each type of usage.$49 /mo · planned

Enterprise · Discuss usage, retention and support requirements with us.Custom

Pro usage pricing is planned. Confirm availability and terms with us before purchasing.

What we need from you

A GitHub organization admin for the install, five minutes. A Slack channel. The standards document you already have.

Discuss a pilot

Install free