Skip to content

Commit 6849380

Browse files
Docs for "Push Rulesets - [GA]" (#51686)
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
1 parent f224787 commit 6849380

File tree

8 files changed

+4
-20
lines changed

8 files changed

+4
-20
lines changed

content/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ You can create rulesets in your organization to control how users can interact w
1717

1818
{% data reusables.repositories.rulesets-push-rulesets-intro %}
1919

20-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
21-
2220
{% endif %}
2321

2422
Forks do not inherit branch or tag rulesets from their upstream repositories. However, forks owned by your organization are subject to the rulesets you create, like any other repository.
@@ -88,9 +86,7 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
8886

8987
## Creating a push ruleset
9088

91-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
92-
>
93-
> This ruleset will enforce push restrictions for this repository's entire fork network.
89+
{% data reusables.repositories.push-rules-fork-network-note %}
9490

9591
You can create a push ruleset for private or internal repositories in your organization.
9692

content/pull-requests/collaborating-with-pull-requests/getting-started/best-practices-for-pull-requests.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,8 +60,6 @@ You can use protected branches to prevent pull requests from being merged into i
6060

6161
### Use push rulesets
6262

63-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
64-
6563
{% data reusables.repositories.push-rulesets-overview %}
6664

6765
For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#push-rulesets)."

content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,6 @@ Public forks do not inherit the permissions structure of the upstream repository
4444

4545
### About push rulesets for forked repositories
4646

47-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
48-
4947
{% data reusables.repositories.rulesets-push-rulesets-fork-network-information %}
5048

5149
For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#push-rulesets)."

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,6 @@ For organizations on the {% data variables.product.prodname_enterprise %} and {%
2626

2727
You can use rulesets to target branches or tags in a repository or to block pushes to a repository and the repository's entire fork network.
2828

29-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
30-
3129
{% endif %}
3230

3331
{% ifversion push-rule-delegated-bypass %}
@@ -46,8 +44,6 @@ For each ruleset you create, you specify which branches or tags in your reposito
4644

4745
### Push rulesets
4846

49-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
50-
5147
{% data reusables.repositories.push-rulesets-overview %}
5248

5349
{% endif %}

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ You can create rulesets to control how users can interact with selected branches
1818

1919
{% data reusables.repositories.rulesets-push-rulesets-intro %}
2020

21-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
22-
2321
{% endif %}
2422

2523
When you create a ruleset, you can allow certain users to bypass the rules in the ruleset.
@@ -85,9 +83,7 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
8583

8684
## Creating a push ruleset
8785

88-
{% data reusables.repositories.rulesets-push-rules-beta-note %}
89-
>
90-
> This ruleset will enforce push restrictions for this repository's entire fork network.
86+
{% data reusables.repositories.push-rules-fork-network-note %}
9187

9288
You can create a push ruleset for private or internal repositories.
9389

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
> [!NOTE]
2+
> This ruleset will enforce push restrictions for this repository's entire fork network.

data/reusables/repositories/rulesets-push-rules-beta-note.md

Lines changed: 0 additions & 1 deletion
This file was deleted.
Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1 @@
11
Your repository may have push rulesets enabled. Push rulesets may block creating a new file in the repository based on certain restrictions. Push rulesets apply to the repository's entire fork network. Which means that any push rulesets that are configured in the root repository will also apply to every fork of the repository. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#about-rulesets)."
2-
{% data reusables.repositories.rulesets-push-rules-beta-note %}

0 commit comments

Comments
 (0)