Skip to content

fix(notifications): enrich disposition notifications with the gate verdict#6650

Closed
nghetienhiep wants to merge 1 commit into
JSONbored:mainfrom
nghetienhiep:fix/issue-6636
Closed

fix(notifications): enrich disposition notifications with the gate verdict#6650
nghetienhiep wants to merge 1 commit into
JSONbored:mainfrom
nghetienhiep:fix/issue-6636

Conversation

@nghetienhiep

Copy link
Copy Markdown
Contributor

fix(notifications): enrich disposition notifications with the gate verdict

The action executor's per-repo Discord/Slack notification used the plain
disposition reason (action.reason) as its summary. resolveDispositionReason —
built to surface the AI's recorded gate verdict for exactly this notification —
was left with no call site once #2881 migrated notifications off the
pull_request.closed path and onto the executor, so the enriched, verdict-aware
reason its doc comment promises never reached users.

Wire resolveDispositionReason into the executor's notify path so a terminal
merge/close/request_changes notification shows the latest recorded gate_decision
summary for the PR, falling back to the plain disposition reason when no verdict
is on record or the read fails.

Closes #6636

…rdict

The action executor's per-repo Discord/Slack notification used the plain
disposition reason (action.reason) as its summary. resolveDispositionReason —
built to surface the AI's recorded gate verdict for exactly this notification —
was left with no call site once JSONbored#2881 migrated notifications off the
pull_request.closed path and onto the executor, so the enriched, verdict-aware
reason its doc comment promises never reached users.

Wire resolveDispositionReason into the executor's notify path so a terminal
merge/close/request_changes notification shows the latest recorded gate_decision
summary for the PR, falling back to the plain disposition reason when no verdict
is on record or the read fails.

Closes JSONbored#6636
@nghetienhiep
nghetienhiep requested a review from JSONbored as a code owner July 16, 2026 17:09
@JSONbored

Copy link
Copy Markdown
Owner

Banned.

@superagent-security

Copy link
Copy Markdown
Contributor
\nSuperagent didn't find any vulnerabilities or security issues in this PR.

@JSONbored JSONbored added the banned Banned due to plagiarism or other repeat violations. label Jul 16, 2026
@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 16, 2026
@codecov

codecov Bot commented Jul 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.64%. Comparing base (268b528) to head (0143a2b).
⚠️ Report is 15 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #6650       +/-   ##
===========================================
+ Coverage   70.33%   93.64%   +23.31%     
===========================================
  Files         680      680               
  Lines       68024    68025        +1     
  Branches    18671    18671               
===========================================
+ Hits        47845    63703    +15858     
+ Misses      16225     3347    -12878     
+ Partials     3954      975     -2979     
Flag Coverage Δ
shard-1 43.93% <100.00%> (?)
shard-2 36.99% <100.00%> (+0.09%) ⬆️
shard-3 32.40% <0.00%> (?)
shard-4 33.76% <100.00%> (?)
shard-5 31.61% <0.00%> (?)
shard-6 45.78% <100.00%> (+0.07%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
src/services/agent-action-executor.ts 96.96% <100.00%> (+38.52%) ⬆️

... and 380 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

banned Banned due to plagiarism or other repeat violations. gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

resolveDispositionReason is fully implemented and tested but never called from production code

2 participants