Context
Bulk-aligned first-party DataKnifeAI repos to docs/REPO_SETTINGS.md (solo-dev pattern) via GitHub API on 2026-08-02.
Applied across public first-party repos:
- Wiki off, downloads off, squash on,
delete_branch_on_merge on, allow_update_branch on
- Vulnerability alerts + Dependabot security updates on
- Classic
main protection: PR required, 0 approvals, dismiss stale, conversation resolution, linear history, no force-push/delete, enforce_admins off, empty required-check lists cleared
Remaining manual gaps
Private repos — branch protection unavailable (403)
Free / current plan blocks classic branch protection on private repos:
| Repo |
Notes |
VideosRipper |
Settings + vuln/depsec applied; protection 403 |
gitops-fleet |
Settings + vuln/depsec applied; protection 403 |
Options: upgrade plan for private protection, or make sensitive repos public with careful secrets hygiene.
Org-level rulesets
Org rulesets were not readable/writable without admin:org scope. Consider encoding the solo-dev defaults as an org ruleset so new repos inherit them (when a token with admin:org is available).
Dependabot version updates (dependabot.yml)
Security updates were enabled via API. Version-update configs (.github/dependabot.yml) remain opt-in per ecosystem — do not bulk-add; wire per repo when lockfiles/manifests exist.
Required status checks
Cleared empty/strict-with-no-contexts lists. When callers pin reusable workflows from github-workflows, add the real check names to protection (do not invent).
Forks (intentionally not fully aligned)
| Fork |
Notes |
truenas-csi |
issues off, main |
satisfactory-server-k8s |
issues off, main |
windrose-server-k8s |
issues off, main |
xone |
issues off, default master (upstream) |
democratic-csi |
issues off, default master; wiki turned off only |
Leave forks alone unless graduating to first-party products.
Done / no action needed
- First-party public repos: settings + solo protection aligned
.github meta repo protection already matched solo pattern before this pass
Context
Bulk-aligned first-party DataKnifeAI repos to
docs/REPO_SETTINGS.md(solo-dev pattern) via GitHub API on 2026-08-02.Applied across public first-party repos:
delete_branch_on_mergeon,allow_update_branchonmainprotection: PR required, 0 approvals, dismiss stale, conversation resolution, linear history, no force-push/delete,enforce_adminsoff, empty required-check lists clearedRemaining manual gaps
Private repos — branch protection unavailable (403)
Free / current plan blocks classic branch protection on private repos:
VideosRippergitops-fleetOptions: upgrade plan for private protection, or make sensitive repos public with careful secrets hygiene.
Org-level rulesets
Org rulesets were not readable/writable without
admin:orgscope. Consider encoding the solo-dev defaults as an org ruleset so new repos inherit them (when a token withadmin:orgis available).Dependabot version updates (
dependabot.yml)Security updates were enabled via API. Version-update configs (
.github/dependabot.yml) remain opt-in per ecosystem — do not bulk-add; wire per repo when lockfiles/manifests exist.Required status checks
Cleared empty/strict-with-no-contexts lists. When callers pin reusable workflows from
github-workflows, add the real check names to protection (do not invent).Forks (intentionally not fully aligned)
truenas-csimainsatisfactory-server-k8smainwindrose-server-k8smainxonemaster(upstream)democratic-csimaster; wiki turned off onlyLeave forks alone unless graduating to first-party products.
Done / no action needed
.githubmeta repo protection already matched solo pattern before this pass