Run outcomes: refusal and no-op must not report bare Succeeded
Maintainers usually reply within 1 day
@ibolton336 is already working on this.
Since Oct 5, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with ADR 0011 and issue #119 to understand the existing termination and exit-code contract, then inspect the E2E coverage for run status and the outcome reporting mentioned in PR #114. Done means a refused gate is not reported as Succeeded, and a no-change run is distinguishable from a changed run in the UI-facing status.
Written by the indexing model from the issue text.
Description
Today a stage-gate refusal still reports Succeeded — #96 fixed cancels only. Define the outcome contract — refused / failed / succeeded / succeeded-with-no-changes — and surface it on run status for the UI. Frame it as an extension of ADR 0011's exit-code contract: exit 2 → LimitReached (#119) is the precedent; a refusal wants the same shape, not a bespoke channel. Related hook: the "results pushed" notice overstates outcomes the same way — flagged in PR #114.
Done when:
- E2E shows a refused gate ≠
Succeeded. - A no-change run is distinguishable from a changed one.
Depends on: #119 (rides the same termination mechanism).
- Dominant language
- Go
- Stars
- 5
- Forks
- 13
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 41
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from konveyor/agentic-controller
-
bug stream/controller
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
konveyor/agentic-controller#164 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
konveyor/agentic-controller#124 · 1 comment ·
Maintainers usually reply within 1 day
-
The verification pass cannot read the Verification section a real plan wrote, and runs a line of its prose as a commandPossibly taken @ibolton336 claimed this today. Openbug stream/controller
konveyor/agentic-controller#336 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
konveyor/agentic-controller#323 ·
Maintainers usually reply within 1 day
-
Provider-aware Gateway verification for aws-bedrock / gcp-vertex-ai, so bad credentials fail at verify rather than mid-runPossibly taken @ibolton336 claimed this 2 days ago. Openenhancement stream/controller
konveyor/agentic-controller#304 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in konveyor/agentic-controller
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SAP/crossplane-provider-btp#1175 ·
Maintainers usually reply within 1 day
-
adk: stream concatenation errors bypass retry and failoverPossibly taken @OUAO-FRANK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google/osv-scalibr#2586 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stacklok/toolhive-catalog#1890 ·
Maintainers usually reply within 1 day
-
heap: pushing an item that is already queued corrupts the indexPossibly taken @lbarrosby claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kubernetes-sigs/kwok#1800 ·
Maintainers usually reply within 1 day