Events is the space-wide activity record behind live cards, attention, rules, and reports. Use it to move from “something needs attention” to the exact delivery event and evidence.
What appears
- Pull requests and their review/check state.
- Linked GitHub or Linear issues when Warestack has the association.
- Workflow runs and failures.
- Deployments and deployment reviews.
- Rule findings and attention reasons.
- Pull-request stack position and readiness when the PR belongs to a stack.
Find what matters
Filter the feed by repository, event type, status, actor, time window, or whether an item needs attention. Overview › Needs attention links into the same evidence with a personal or space-wide lens.
When a space is first connected, the GitHub import can bring in recent events (up to the supported import window) so the feed is useful before the next webhook arrives. Historical data is evidence for inspection; enabling a chain does not send retroactive Slack notifications.
Open an event
A pull-request event page can bring together:
- Repository, branch, author, state, and diff statistics.
- Linear association.
- Requested reviewers, submitted reviews, checks, and review threads.
- Related workflows and deployments.
- Warestack rule findings.
- A chronological timeline.
The product calls this Events and Timeline. “Change trace” in design or planning material refers to this job; it is not a separate shipped route.
Findings
Findings distinguish unresolved, acknowledged, and resolved evidence. The console displays the current finding and its context. A space admin can acknowledge an eligible blocking finding in the console only after supplying a reason. Warestack audits the action and refreshes the GitHub check. The exception is revision-bound: it applies only to that exact evaluated pull-request head and finding, so a new head or materially changed finding becomes enforceable again. This is a targeted acknowledgement, not a general exception register with owner and expiry.
From event to action
| Observation | Next surface |
|---|---|
| Requested review is waiting | Review SLA |
| Same-repository dependent PRs | PR stacks |
| Rule finding | Rules or /warestack violations |
| A person needs the item | Overview and attention |
| Chain execution needs inspection | Automations › Activity |
| Period needs sampling | Reports |
Honesty
An event timeline records what Warestack received. A known ticket reference can become a persisted association, but an unresolved string is not proof; nor is a bot a human or a pending deployment a successful production rollout.