Skip to content

Custom properties

Custom properties allow you to decorate your repository with information such as compliance frameworks, data sensitivity, or project details.

all-green
true
Repositories with this property will require to have a `All Green` check to complete Pull Requests. Changes require an org owner and justification. New repos default to true even if user changes it on repository creation.
classification
confidential
Defines the information sensitivity level of the repository content. Used to enforce access control, compliance, and data handling policies according to internal security guidelines.
conventional-commits
true
Enforce conventional commits across the repository. All repositories must follow the conventional commits by default. Changes require an org owner and justification. New repos default to true even if user changes it on repository creation.
copilot-review
true
Request Copilot code review for new pull requests automatically if the author has access to Copilot code review and their premium requests quota has not reached the limit.
criticality
medium
Indicates the criticality level of the repository based on its business impact, availability requirements, and risk tolerance. This property helps prioritize support, monitoring, and governance efforts accordingly.
development-flow
github-flow
Define the branching and merge strategy used in the repository, such as github-flow (feature branches squashed into main) or long-running branches (develop/staging alongside main) allowing merge commits.
email-commit-filter
true
Enables the filter to only accepts emails from blip and allowed domains. Changes require an org owner and justification. New repos default to true even if user changes it on repository creation.
only-codeowners
false
Disable repo-level approvals and rely only on CODEOWNERS. Changes require an org owner and justification. New repos default to true even if user changes it on repository creation.
product-cycle
ga
Represents the current stage of the repository within the product lifecycle. Useful for aligning development practices, review rigor, and deprecation policies based on the maturity of the system.