GitHub Actions
Runs the gate and gives Strake deploy history, workflow status, and dependency-change context.
Connect the stack you already trust.
Strake reads the operational signals your team already produces and puts them in the PR deploy decision.
GitHub Actions
Available
PR verdicts, deploy history, dependency movement
PagerDuty
Available
Active incidents and service context
Datadog
Limited
SLO and health context when configured
Slack
Planned
Notifications after the PR workflow is proven
PagerDuty
Adds active incident and service context so teams do not deploy into known fire.
Datadog
Provides SLO and health context when configured for the services you care about.
Slack planned
Notifications are planned after the PR workflow earns trust. Today, verdicts live in GitHub and Strake.
Coverage model
Strake shows what it can see.
The product should be honest about connected and missing sources. A limited view is still useful when the team understands the confidence level.
GitHub Actions
Available
PR verdicts, deploy history, dependency movement
PagerDuty
Available
Active incidents and service context
Datadog
Limited
SLO and health context when configured
Slack
Planned
Notifications after the PR workflow is proven
1
Start in GitHub
Install the Action and prove that a PR verdict is useful on a real production workflow.
2
Add incidents
Connect PagerDuty so active incidents and service context influence the deploy decision.
3
Expand health
Layer in Datadog context for SLO and system health once your first repo is producing useful feedback.
Connect one signal path first.
Install the GitHub Action, open a pull request, and judge the verdict before adopting anything else.