Settings · Custom properties · github/site-policy · GitHub

client-appIndicates whether this repository builds or distributes a client application.false

CodeQL-BlockBreak glass for CodeQL required workflow preventing merging PRstrue

dependency-review-action-enabledWhether or not dependency-review should run on an individual repotrue

deployableDOES NOT GATE DEPLOYS

This indicates if the code present in the repository is "deployable", i.e. deployable to Moda or via Heaven.
Managed by enterprise-security, please raise questions in #enterprise-security in slack.false

durable-ownership-check-enabledWhen `true` it will make given repository in scope for `Durable Ownership Check` ruleset(s).

https://thehub.github.com/epd/engineering/products-and-services/internal/service-catalog/ownership-enforcementfalse

enforce_sha_pintrue

OPENGREP_ANALYSISThis property enables the Opengrep required workflow: https://github.com/github/opengrep-workflowtrue

ospo-license-check"On" to target for license compliance checks, "Off" to not, but this could be reset by automation. "Skip" means to not allow automation to reset the property (don't use for repositories with code)On

ownership-nameThis field will contain either the name of the Service Catalog entry or the Hubber’s handle. For Hubber handles or Teams, we will support both formats: with and without the “@” symbol. For Teams, please provide the full name (e.g., @github/myteam)site-policy

ownership-typeWhether a repository is owned by a Service Catalog entry or an individual Hubber. In some instances, such as repos for CoB or interest groups, you may select `Team` instead.Service Catalog

repo-mirror-ciControls whether CI is turned on in the Resiliency Mirror for this repodisabled

repo-mirror-strategySet this property to desired mirror strategy for Resiliency Mirror Manager (see: https://github.com/github/resiliency-mirror-manager) automation.standard