GitHub announced Copilot custom property suggestions on September 15, 2026. The public preview helps administrators define allowed values for repository metadata and is available with Copilot Business and Copilot Enterprise. For QA teams, the practical connection is governance: repository properties can determine which repositories a ruleset targets.

What changed

When administrators create a property definition at organization or enterprise level, Copilot suggests relevant choices. GitHub illustrates this with compliance-related options for a multi-select property and yes/no options for an internet-facing single-select property. Administrators can accept suggestions, while enterprise and organization owners control availability through the Repository custom property suggestions Copilot policy. These details come from the September 15 GitHub announcement.

The preview concerns suggested values during schema creation. The announcement does not establish automatic repository classification or automatic ruleset creation.

Why this matters for QA engineers

Our QA assessment: an inconsistent property vocabulary can make a governance rule cover the wrong repositories. AI assistance may reduce setup effort, but teams still need evidence that the resulting metadata selects the intended scope.

GitHub’s custom properties documentation explains that required properties can have defaults, and repositories without explicit values inherit those defaults. It also documents repository filtering by property value. Those existing behaviors are useful validation points when adopting the new suggestions.

Recommended rollout checks

  • Review vocabulary: compare suggested choices with the team’s approved repository classifications before accepting them.
  • Test defaults: include repositories with explicit values and inherited defaults in the pilot.
  • Check targeting: verify that intended repositories match the relevant ruleset and unrelated repositories remain outside its scope.
  • Record evidence: capture the accepted schema, sample repository values and observed rule coverage before expanding adoption.

These are QATechTools recommendations, not capabilities promised by the preview. Source information verified September 16, 2026.