On the Team and Enterprise plans, an organization owner can define rulesets once, under the organization's Settings, Repository, Rulesets, and apply them to all repositories, a hand-picked list, names matching a pattern (booknest-*), or repositories with a custom property such as team: catalog. Repository admins cannot weaken them, since the strictest rule wins. On GitHub Enterprise 29 , Evaluate mode records what a new ruleset would block without blocking anything. The API call goes to orgs/{org}/rulesets with a repository_name condition. BookNest has no organization, so this is not run here.