Custom Properties Now Enforce Explicit Values

Organization and enterprise administrators can now require repository creators to explicitly select values for custom properties, rather than relying on default values. This ensures repositories meet policy requirements from the moment they're created, improving adoption of rulesets and data accuracy across your organization.

Previously, the asterisk (*) on the repository creation page indicated a required property that could accept a default value. With this update, the asterisk now clearly indicates properties requiring explicit selection, giving administrators tighter control over repository configuration and ensuring no policies are inadvertently bypassed through defaults.

Rule Insights Get Dynamic Filtering with SHA Support

The rule insights experience has been improved with a new dynamic filter bar replacing the previous dropdown-based filters. The key enhancement is support for filtering by commit SHA on the repository-level rule insights page, making it significantly easier to understand how specific commits interacted with your rulesets.

This more flexible filtering approach provides a consistent experience and better visibility into rule activity, helping teams debug issues and understand ruleset behavior across their repositories.

What You Need to Do

• For custom properties: Review your organization's custom property configurations to determine which properties should require explicit selection versus defaults
• For rule insights: Leverage the new SHA filtering to troubleshoot specific commits and verify ruleset compliance