GitHub Enterprise Server 3.22 发布候选版本

GitHub Enterprise Server (GHES) 3.22 is now available and introduces new capabilities across the platform. Here are a few highlights in the 3.22 release: Administrators can configure Copilot CLI to work with GHES for enterprises that operate in disconnected or air-gapped environments without connectivity to GitHub Cloud. Set up a model provider once in GHES, and your end users across the enterprise can use Copilot CLI with their GHES credentials. This capability is in technical preview and is subject to change. Enterprise Teams, previously in public preview, is now generally available. Enterprise owners can use Enterprise Teams to manage users and their access across the entire enterprise, including organizations and repositories, from a single, centralized team structure. This reduces the operational overhead of managing user access across multiple organizations within an enterprise. Enterprise Teams, previously in public preview, is now generally available. Enterprise owners can use Enterprise Teams to manage users and their access across the entire enterprise, including organizations and repositories, from a single, centralized team structure. This reduces the operational overhead of managing user access across multiple organizations within an enterprise. Security analysts can now sort secret scanning push protection bypass requests and secret scanning alert dismissal requests by date, in ascending or descending order, using the filter bar at the repository, organization, and enterprise levels. Previously, sort order for these requests could not be adjusted, which made it difficult for teams managing high volumes of requests to prioritize their review. Security analysts can now sort secret scanning push protection bypass requests and secret scanning alert dismissal requests by date, in ascending or descending order, using the filter bar at the repository, organization, and enterprise levels. Previously, sort order for these requests could not be adjusted, which made it difficult for teams managing high volumes of requests to prioritize their review. Repository rulesets now support bypassing by individual users. This gives administrators more granular control over rule bypass permissions, such as adding a service account to a bypass list without needing to create a dedicated role or team. Repository rulesets now support bypassing by individual users. This gives administrators more granular control over rule bypass permissions, such as adding a service account to a bypass list without needing to create a dedicated role or team. Organization owners and repository administrators can require specific reviewers for pull requests by adding a required reviewers rule to a repository ruleset, targeting specific branches, files, and folders using pattern matching, and can set the minimum number of required reviews per team. This rule works alongside CODEOWNERS and is particularly useful when changes need sign-off from teams beyond the code owners (e.g., security, QA, or design). For example, administrators can require a data platform team review on all *.sql changes, security team members on the default branch, or product and design reviewers on feature branches. Organization owners and repository administrators can require specific reviewers for pull requests by adding a required reviewers rule to a repository ruleset, targeting specific branches, files, and folders using pattern matching, and can set the minimum number of required reviews per team. This rule works alongside CODEOWNERS and is particularly useful when changes need sign-off from teams beyond the code owners (e.g., security, QA, or design). For example, administrators can require a data platform team review on all *.sql changes, security team members on the default branch, or product and design reviewers on feature branches. Developers can now see release status directly in the issue sidebar. When a linked pull request has been included in a release, the sideb