fix(settings): give loopover its own autonomy config-as-code - #6468
Merged
Conversation
Repository_settings had no row at all for JSONbored/loopover, so every agent action class silently defaulted to "observe" (deny-by-default) regardless of review verdict -- reviewed, CI-green, mergeable PRs were never actually merged or closed. Matches the autonomy policy already live in JSONbored/awesome-claude and JSONbored/metagraphed's DB rows, carried instead via .loopover.yml/the bundled self-repo manifest. Also scopes several test fixtures' self-repo identity override (LOOPOVER_DRIFT_ISSUE_REPO) away from "JSONbored/gittensory" so their own DB-configured settings aren't silently replaced by the bundled fallback manifest. Part of #6440
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
loopover-orb
Bot
added
the
gittensor:bug
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6468 +/- ##
==========================================
- Coverage 95.56% 95.56% -0.01%
==========================================
Files 589 589
Lines 47057 47057
Branches 14967 14967
==========================================
- Hits 44972 44970 -2
- Misses 1294 1295 +1
- Partials 791 792 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This was referenced Jul 16, 2026
JSONbored
added a commit
that referenced
this pull request
Jul 16, 2026
… autonomy config-as-code PR #773's autonomy config-as-code change (fix(settings): give loopover its own autonomy config-as-code, merged as PR #6468) replaced the same settings: block section in both .loopover.yml and its bundled fallback manifest, silently dropping this repo's own draftPrClosePolicy: close line in the process — the feature (#6454, merged) has been fully live in code since, just disabled for loopover's own repo because nothing enabled it. Re-add draftPrClosePolicy: close alongside (not replacing) the autonomy: block, in both the committed .loopover.yml and its bundled byte-identical twin.
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
1 participant
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.
Summary
repository_settingshas no row at all forJSONbored/loopover(confirmed via direct DB query), so every agent action class (merge,close,approve,request_changes,update_branch,assign) resolved toDEFAULT_AUTONOMY_LEVEL = "observe"(deny-by-default) regardless of review verdict — reviewed, CI-green, mergeable PRs (e.g. fix(api): open the public no-credential routes to any CORS origin #6401, chore(mcp): remove dead referenceScorePreviewCommand export in local-branch.js #6402) were never actually merged or closed.autonomy:block to.loopover.yml'ssettings:(and its bundled self-repo-fallback twin insrc/config/loopover-repo-focus-manifest.ts), matching the policy already live inJSONbored/awesome-claudeandJSONbored/metagraphed's DB rows — this repo gets the same policy as config-as-code instead of a DB row.LOOPOVER_DRIFT_ISSUE_REPO) away fromJSONbored/gittensoryso their own DB-configured settings in those specific tests aren't silently replaced by the bundled fallback manifest (which now carries this sameautonomy:block).Part of #6440
Scope
wantedPaths(.loopover.yml,src/,test/)site/,CNAME,lovablechangesValidation
npm run test:ci(full local gate, green)npm run test:coverage(unsharded)npm audit --audit-level=moderate(0 vulnerabilities)git diff --check(clean)Safety