GitHub Copilot suggests custom properties definitions
GitHub Copilot can now suggest allowed values when you create a custom property for repositories in your organization. This feature is in public preview for GitHub Copilot Business and Copilot… The post GitHub Copilot suggests custom properties definitions appeared first on The GitHub Blog.
Overview
GitHub Copilot can now suggest allowed values when you create a custom property for repositories in your organization. This feature is in public preview for GitHub Copilot Business and Copilot Enterprise plans.
Custom properties let enterprise and organization admins attach governance metadata to repositories, which you can then use to target repositories with rulesets. Custom properties are one of the most popular ways to scope rulesets, but getting started has been a challenge. Admins often aren’t sure which properties to define or what allowed values to use, and inconsistent metadata makes it harder to apply governance consistently across a large fleet of repositories.
With this release, when you create a new custom property definition at the enterprise or organization level, Copilot will suggest relevant allowed values based on the property you’re defining. For example:
- Creating a multi-select property like
FedRAMPsurfaces suggested compliance-related values. - Creating a single-select property like
internet-facingsurfaces suggested values such asyesandno.
You can accept a suggestion in one click, helping you stand up a meaningful custom property taxonomy faster.
Details
Enterprise and organization owners can now configure the Repository custom property suggestions Copilot policy to control feature availability.
Learn more in our docs about managing custom properties for repositories in your organization.
Cookie Preferences
The post GitHub Copilot suggests custom properties definitions appeared first on The GitHub Blog.
Source
Originally published at github.blog.
