Connect repository
Connect your GitHub repository
Install or connect Dulvarn to the repository you release from. Dulvarn reads PR metadata, changed files and configured repository policy.
- repository
- branch
- PR metadata
- release policy
Dulvarn connects PR changes, CI results, test signals and repository policy into one clear workflow for release risk review.
Your team keeps control. Dulvarn explains what changed, what is risky, what should be tested and whether the release is GO, CONDITIONAL GO or NO-GO.
Dulvarn does not replace your QA process. It makes the release decision path explicit, reviewable and traceable.
Install or connect Dulvarn to the repository you release from. Dulvarn reads PR metadata, changed files and configured repository policy.
Define thresholds and rules that influence GO, CONDITIONAL GO and NO-GO outcomes.
Dulvarn evaluates changed files, affected areas and risky hotspots before the release decision is produced.
CI can be green while product risk remains unclear. Dulvarn combines CI state with test integrity and impact signals.
Dulvarn recommends Smoke, Partial NRT or Full NRT based on risk, impact and policy.
The result is a decision summary with reasons, risk score, test integrity score and recommended next actions.
QA or release owner reviews the evidence, approves or overrides the decision with a reason. Every decision is stored in the audit trail.
A representative example of how Dulvarn would evaluate a real-looking PR.
CI is passing, but the change touches checkout and payment retry logic while impacted test coverage is incomplete. Dulvarn recommends Partial NRT before human release approval.
A release decision combines code risk, CI state, test integrity, test impact and repository policy.
Changed files, touched flows, hotspots and complexity.
Passing, failing or unknown CI status.
Whether mapped tests exist and whether coverage looks strong enough.
Which suites are relevant to the changed areas.
Thresholds configured by the team.
Whether a reviewer must add a reason before overriding.
The exact policy can be configured per repository. Dulvarn explains the decision so humans can review it.
Dulvarn helps the team avoid guessing regression scope.
Best for low-risk changes where critical flows are not affected and test integrity is healthy.
Best for medium-risk changes that affect specific product areas such as checkout, auth or payments.
Best for broad, high-risk releases, failing CI, low test integrity or changes across critical flows.
Dulvarn is intentionally designed as decision support, not autonomous release control. QA Leads, Release Managers and Engineering Leads keep ownership of the final release decision.
Dulvarn fits into the tools teams already use for PR review, CI and release preparation.
Triggered on pull request events and updates.
Release decision can surface as a PR status.
Risk summary and reasoning surfaced on the PR.
Reads CI status and test results as evidence.
Required checks and release rules per repo.
Every decision and override retained per repository.
Designed for GitHub-first workflows · integration depth depends on beta setup.
Dulvarn is currently being tested with QA and engineering teams that want clearer release decisions, better test scope recommendations and fewer production surprises.