KEMBAR78
[ci] Add branch classification file by rmarinho · Pull Request #31292 · dotnet/maui · GitHub
Skip to content

Conversation

rmarinho
Copy link
Member

Description of Change

This pull request introduces a branch classification configuration to the repository. The new configuration file defines which branches are considered production versus non-production, helping to enforce policies and improve clarity around branch usage.

Branch classification configuration:

  • Added .azuredevops/policies/branchClassification.yml to specify branch classification settings, marking main, release/*, net10.0, net9.0, and inflight/current as production branches, with all others defaulting to nonproduction.

@Copilot Copilot AI review requested due to automatic review settings August 22, 2025 12:27
@rmarinho rmarinho requested a review from a team as a code owner August 22, 2025 12:27
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a branch classification configuration file to help categorize branches as production or non-production within the Azure DevOps environment. This configuration will enable policy enforcement and provide clearer governance around branch usage patterns in the repository.

  • Adds a new YAML configuration file defining branch classification rules
  • Designates key branches (main, release/*, version-specific branches, and inflight/current) as production branches
  • Sets default classification to nonproduction for all other branches

@rmarinho rmarinho merged commit 2bcf985 into main Aug 22, 2025
1 of 22 checks passed
@rmarinho rmarinho deleted the default-branches branch August 22, 2025 12:27
@rmarinho rmarinho added this to the .NET 10.0-rc1 milestone Aug 22, 2025
@rmarinho rmarinho moved this from Todo to Done in MAUI SDK Ongoing Aug 22, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Sep 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant