Merge pull request #45413 from github/repo-sync

Repo sync

Author: docs-bot

assets/images/help/models/github-models-commit-changes.png

@@ -1,10 +1,21 @@
-## Managing requests to bypass push rules
+---
+title: Managing requests to bypass push rules
+intro: View and manage requests for bypass privileges to push commits containing restricted content to a repository.
+allowTitleToDifferFromFilename: true
+permissions: Enterprise owners
+versions:
+  feature: repo-policy-rules
+shortTitle: Manage requests to bypass push rules
+contentType: how-tos
+category:
+  - Manage accounts and repositories
+---
 
 > [!NOTE] Repository policy delegated bypass is in {% data variables.release-phases.public_preview %} and subject to change.
 
 You can view and manage all requests for bypass privileges on the “Bypass Requests" page, located under the **Policy** settings.
 
-You can filter requests by approver (member of the bypass list), requester (contributor making the request), timeframe, and status. The following statuses are assigned to a request:
+Filter requests by approver (member of the bypass list), requester (contributor making the request), timeframe, and status. The following statuses are assigned to a request:
 
 |Status|Description|
 |---------|-----------|

assets/images/help/models/github-models-compare-toggle.png

@@ -8,14 +8,14 @@ shortTitle: Govern repository usage
 contentType: how-tos
 category:
   - Manage accounts and repositories
+redirect_from:
+  - /enterprise-onboarding/govern-people-and-repositories/create-repository-policies
 ---
 
 {% data reusables.enterprise.repo-policy-rules-preview %}
 
 {% data reusables.enterprise.repo-policy-rules-intro %}
 
->[!TIP] If you're an **organization owner**, you can create a repository policy for a specific organization. See [AUTOTITLE](/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization).
-
 ## Examples
 
 {% data reusables.enterprise.repo-policy-rules-examples %}
@@ -24,7 +24,9 @@ category:
 
 First, you'll target organizations in your enterprise. You can select all organizations, choose from a list, or create a dynamic rule using `fnmatch` syntax. If you use {% data variables.product.prodname_emus %}, you can also choose to target all repositories owned by users in your enterprise.
 
-Then, you'll target repositories in the selected organizations. {% data reusables.enterprise.repo-policy-rules-with-custom-properties %}
+Then, you'll target repositories in the selected organizations. We recommend using repository policies alongside **custom repository properties**. By adding custom properties to repositories, you can flexibly target those repositories in a policy.
+
+For example, you can add a property to mark repositories that contain production data or other sensitive information, then prevent anyone from making those repositories public.
 
 ## Interaction with other policies
 
@@ -73,11 +75,3 @@ Choose which repositories (current or future) to target in the selected organiza
 ### Delegating bypass of policies
 
 {% data reusables.enterprise.repo-policy-rules-delegated-bypass %}
-
-#### Managing bypass requests
-
-{% data reusables.enterprise.repo-policy-rules-manage-bypass-request %}
-
-## Further reading
-
-To set additional policies for repository management, see [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise).

assets/images/help/models/github-models-datasets.png

@@ -10,6 +10,7 @@ versions:
   ghes: '*'
 children:
   - /governing-how-people-use-repositories-in-your-enterprise
+  - /bypass-push-rules-requests
   - /viewing-user-owned-repositories-in-your-enterprise
   - /accessing-user-owned-repositories-in-your-enterprise
   - /managing-custom-properties-for-repositories-in-your-enterprise

assets/images/help/models/github-models-system-prompt.png

@@ -37,7 +37,6 @@ For more information about how {% data variables.product.prodname_ai_credits_sho
 * Your license usage is calculated based on the number of unique, active committers to repositories with {% data variables.product.prodname_code_quality_short %} enabled. 
 * Each **active committer** uses **one {% data variables.product.prodname_code_quality_short %} license**. 
 * A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
-* A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
 
 To understand your license usage, and which licenses you can free up, it helps to distinguish between active and unique committers. You can see the number of licenses you're using on the **Licensing** page for your organization or enterprise, shown as **"Consumed licenses"**:
 * **Active committers** are committers who contributed to at least one repository and have a {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} license with your organization or enterprise. This includes members, enterprise-managed users, external collaborators, and people with a pending invitation to join your organization or enterprise.