fix(review): fold review.linkedIssueSatisfaction into the real gate as an alias (#4149) - #4811
Merged
Merged
Conversation
…s an alias (#4149) Two near-identically-named fields existed, and only one did anything: gate.linkedIssueSatisfaction (RepositorySettings.linkedIssueSatisfactionGateMode) is the real, DB-backed gate mode that actually runs the AI assessment and can block a PR. review.linkedIssueSatisfaction (FocusManifestReviewConfig, #2173) was parsed and validated but never read anywhere -- a silent no-op a self-host operator could easily set by mistake given the near-identical name, with no warning and no effect. resolveEffectiveSettings now falls back to review.linkedIssueSatisfaction when gate.linkedIssueSatisfaction is unset, mirroring the same gate: > (alias) precedence already used for #4618's linkedIssuePolicy fold-in -- setting either spelling now has the same real effect, and an explicit gate.linkedIssueSatisfaction still always wins when both are set.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4811 +/- ##
=======================================
Coverage 94.22% 94.22%
=======================================
Files 441 441
Lines 38745 38747 +2
Branches 14106 14107 +1
=======================================
+ Hits 36508 36510 +2
Misses 1577 1577
Partials 660 660
🚀 New features to boost your workflow:
|
This was referenced Jul 11, 2026
Closed
1 task
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4149.
Summary
Two near-identically-named fields existed, and only one did anything:
gate.linkedIssueSatisfaction(RepositorySettings.linkedIssueSatisfactionGateMode) — the real, DB-backed gate mode that actually runs the AI assessment and can block a PR (linked_issue_scope_mismatch, confirmed-contributor-gated).review.linkedIssueSatisfaction(FocusManifestReviewConfig, feat(config): add review.linkedIssueSatisfaction config knob (off/advisory/block, default off) #2173) — parsed and validated, but never read anywhere insrc/. A silent no-op: a self-host operator could easily set the wrong one by name confusion and get no warning, no effect.resolveEffectiveSettingsnow falls back toreview.linkedIssueSatisfactionwhengate.linkedIssueSatisfactionis unset (null), mirroring the exact samegate:> alias precedence already established for #4618'slinkedIssuePolicyfold-in earlier tonight. Setting either spelling now has the same real effect; an explicitgate.linkedIssueSatisfactionstill always wins when both are set.Both value sets are identical (
GateRuleModeandLinkedIssueSatisfactionModeare both"off" | "advisory" | "block"), so the fold-in is a direct assignment with no value translation needed.Test plan
npx tsc --noEmit— cleanselfhost-ai.test.ts, confirmed to pass cleanly in isolation — zero relation to this change, timing-sensitive under system load)npm run docs:drift-check,npm run manifest:drift-check,npm run engine-parity:drift-check— all passnpm audit --audit-level=moderate— 0 vulnerabilitiesreview.linkedIssueSatisfactiontaking effect whengate.linkedIssueSatisfactionis unset,gate.linkedIssueSatisfactionalways winning when both are set, falling through to the DB value when neither is set, andreview.linkedIssueSatisfaction: offapplying as a real distinct value (not silently skipped as falsy)