feat(settings): add configurable per-repo blacklistLabel (#1425) - #1430
Merged
Conversation
Adds `blacklistLabel`, a per-repo configurable label (default "slop") for the contributor-blacklist disposition, wired with full config-as-code parity: DB column + migration, Drizzle/types, the focus-manifest (.gittensory.yml) resolver, OpenAPI, and the settings route. This is the management/config layer for the anti-abuse blacklist; the engine disposition that consumes it lands in a follow-up. The label is configurable so the disposition works regardless of the label a repo uses — nothing is hard-coded. Advances #1425.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | eb90475 | Commit Preview URL Branch Preview URL |
Jun 26 2026, 07:48 AM |
8 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1430 +/- ##
=======================================
Coverage 95.39% 95.39%
=======================================
Files 193 193
Lines 20929 20932 +3
Branches 7564 7566 +2
=======================================
+ Hits 19966 19969 +3
Misses 383 383
Partials 580 580
🚀 New features to boost your workflow:
|
8 tasks
This was referenced Jun 26, 2026
Closed
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.
Summary
Adds
blacklistLabel— a per-repo configurable label (defaultslop) the converged engine willapply to a blacklisted contributor's PR/issue — wired with full config-as-code parity so it can be
set from the dashboard/API and as code in
.gittensory.yml. This is the management/config layer ofthe anti-abuse contributor blacklist (#1425); the engine disposition that reads these settings to
label-and-close a banned author lands in the immediate follow-up PR.
The label is configurable (not hard-coded) so the disposition works regardless of the label a repo uses,
mirroring the existing
gittensorLabelsetting end to end.What's wired (every parity site, one PR)
blacklist_labelcolumn (migrations/0073_blacklist_label.sql) + Drizzle schema, defaultslop.RepositorySettings.blacklistLabel(optional; DB always populates it, mirrors the siblingcontributorBlacklist)..gittensory.ymlsettings.blacklistLabelparsed in the focus manifest (> DB > default).RepositorySettingsschema + the settings route (request/response), regeneratedopenapi.json.Scope
wantedPaths; nosite//CNAME/lovable; no changelog edit.Validation
npm run typechecknpm run db:migrations:check(contiguous0001..0073, next free0074)npm run ui:openapi:check(regenerated, matches)npm run test:coverage— full suite green; 100% of changed lines and branches covered (DB round-trip +.gittensory.ymlresolution tests).Safety
min(1).max(50)validation.Advances #1425.