The 3.22 release candidate for GitHub Enterprise Server introduces centralized enterprise team management, refined secret scanning request handling, and granular pull request review rules. These upgrades aim to reduce operational complexity and enhance code review precision for global developer teams.
- Centralized user access via Enterprise Teams lowers admin overhead
- New rulesets enable targeted reviewer mandates per branch or file
- Improved secret scanning request sorting aids security prioritization
Infrastructure signal
GitHub Enterprise Server 3.22 introduces Enterprise Teams as a fully supported feature, enabling organizations to centrally control user access across multiple repositories and organizations within an enterprise. This centralization reduces duplication of access management work and streamlines operational overhead associated with handling permissions at scale.
The release also enhances repository rulesets by allowing bypass permissions to be allocated to specific users instead of teams, facilitating precise control over automated rule exceptions. This adjustment supports smoother platform governance and reduces the need for proliferation of roles or teams just for bypass purposes.
Developer impact
Developers benefit from added visibility into release status directly in issue sidebars, enabling easier tracking of whether fixes are included in releases without context switching. Maintainers gain quick insights into contributor roles from pull request lists, helping prioritize reviews and contextualize contributions effectively.
The ability to specify required reviewers with branch- and file-level granularity through repository rulesets empowers teams to enforce code quality and compliance policies more rigorously. Security, QA, and design teams can now mandate reviews on relevant changes without relying solely on CODEOWNERS files, improving cross-team collaboration during code review.
What teams should watch
Security teams should explore the new filtering options for secret scanning push protection bypass and alert dismissal requests, which now support sorting by date ascending or descending at repository, organization, and enterprise scopes. This feature helps prioritize investigations and improves handling of high-volume alerts.
Platform and admin teams need to assess the impact of enabling Enterprise Teams on existing access governance models to maximize efficiency gains and reduce complexity. Adjusting repository rulesets to control bypass permissions and enforce reviewer mandates will require coordination but can increase security and code quality.
Development teams can leverage improved issue sidebar release indicators and contributor role labels to streamline workflows and better understand the context around contributions and deployment statuses. Monitoring adoption and feedback on these enhancements will be key for refining team processes.