Custom properties and rule insights improvements

Source: GitHub Changelog

Custom properties now support required explicit values

Organization and enterprise administrators can now require repository creators to explicitly select a value for custom properties, rather than relying on a default value.

This ensures repositories meet policy requirements from the moment they’re created, improving adoption of rulesets and the accuracy of property data across your organization.

Previously, the asterisk (*) for custom properties on the repository creation page indicated a required property that accepted a default value. With this update, the asterisk now indicates properties that require an explicit selection so you’ll know exactly which properties need your attention before creating a repository.

Learn more in our documentation about managing custom properties.

Rule insights now feature enhanced filters with SHA support

We’ve replaced the rule insights dropdown filters with a dynamic filter bar, delivering a more flexible and consistent filtering experience.

You can now filter rule insights by commit SHA on the repository-level rule insights page, making it easier to understand how specific commits interacted with rulesets.

Learn more in our documentation about viewing rule insights.

Join the discussion within GitHub Community.