Skip to content

Commit 95e6f3d

Browse files
hectorsectorrachmarimattpollard
authored
Deprecate GHES 3.1 (#28798)
* add 3.1 to deprecated versions * rewrite img src to use azure blob storage in archive script Co-authored-by: rachmari <rachmari@users.noreply.github.com> * remove static files for ghes 3.1 * remove liquid conditionals and content for ghes 3.1 * remove outdated hardware reqs reusable * Fix liquid conditional uncaught by script * Close liquid conditionals missed by script * Apply @mattpollard's suggestions Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: rachmari <rachmari@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
1 parent efaf5f8 commit 95e6f3d

File tree

672 files changed

+873
-1047890
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

672 files changed

+873
-1047890
lines changed

‎content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md

+5-7
Original file line numberDiff line numberDiff line change
@@ -129,18 +129,18 @@ Email notifications from {% data variables.product.product_location %} contain t
129129
| --- | --- |
130130
| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
131131
| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
132-
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li>{% ifversion fpt or ghes or ghae or ghec %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li>{% endif %}<li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
133-
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %}
134-
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %}
132+
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
133+
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |
134+
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
135135

136136
## Choosing your notification settings
137137

138138
{% data reusables.notifications.access_notifications %}
139139
{% data reusables.notifications-v2.manage-notifications %}
140140
3. On the notifications settings page, choose how you receive notifications when:
141141
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
142-
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %}
143-
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %}
142+
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
143+
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% ifversion fpt or ghec %}
144144
- There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}
145145
- There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
146146

@@ -194,15 +194,13 @@ If you are a member of more than one organization, you can configure each one to
194194
5. Select one of your verified email addresses, then click **Save**.
195195
![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif)
196196

197-
{% ifversion fpt or ghes or ghae or ghec %}
198197
## {% data variables.product.prodname_dependabot_alerts %} notification options
199198

200199
{% data reusables.notifications.vulnerable-dependency-notification-enable %}
201200
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
202201
{% data reusables.notifications.vulnerable-dependency-notification-options %}
203202

204203
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
205-
{% endif %}
206204

207205
{% ifversion fpt or ghes or ghec %}
208206
## {% data variables.product.prodname_actions %} notification options

‎content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md

+4-8
Original file line numberDiff line numberDiff line change
@@ -112,15 +112,13 @@ To filter notifications for specific activity on {% data variables.product.produ
112112
- `is:gist`
113113
- `is:issue-or-pull-request`
114114
- `is:release`
115-
- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %}
116-
- `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %}
115+
- `is:repository-invitation`
116+
- `is:repository-vulnerability-alert`{% ifversion fpt or ghec %}
117117
- `is:repository-advisory`{% endif %}
118118
- `is:team-discussion`{% ifversion fpt or ghec %}
119119
- `is:discussion`{% endif %}
120120

121-
{% ifversion fpt or ghes or ghae or ghec %}
122121
For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
123-
{% endif %}
124122

125123
You can also use the `is:` query to describe how the notification was triaged.
126124

@@ -142,8 +140,8 @@ To filter notifications by why you've received an update, you can use the `reaso
142140
| `reason:invitation` | When you're invited to a team, organization, or repository.
143141
| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.
144142
| `reason:mention` | You were directly @mentioned.
145-
| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae or ghec %}
146-
| `reason:security-alert` | When a security alert is issued for a repository.{% endif %}
143+
| `reason:review-requested` | You or a team you're on have been requested to review a pull request.
144+
| `reason:security-alert` | When a security alert is issued for a repository.
147145
| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged.
148146
| `reason:team-mention` | When a team you're a member of is @mentioned.
149147
| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status.
@@ -161,7 +159,6 @@ For example, to see notifications from the octo-org organization, use `org:octo-
161159

162160
{% endif %}
163161

164-
{% ifversion fpt or ghes or ghae or ghec %}
165162
## {% data variables.product.prodname_dependabot %} custom filters
166163

167164
{% ifversion fpt or ghec or ghes > 3.2 %}
@@ -182,4 +179,3 @@ If you use {% data variables.product.prodname_dependabot %} to tell you about in
182179
For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
183180
{% endif %}
184181

185-
{% endif %}

‎content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You can optionally choose to add a description, location, website, and email add
2020

2121
{% ifversion fpt %}
2222
Organizations that use {% data variables.product.prodname_ghe_cloud %} can confirm their organization's identity and display a "Verified" badge on their organization's profile page by verifying the organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" in the {% data variables.product.prodname_ghe_cloud %} documenatation.
23-
{% elsif ghec or ghes > 3.1 %}
23+
{% elsif ghec or ghes %}
2424
To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
2525
{% endif %}
2626

‎content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Setting your profile to private
3-
intro: A private profile displays only limited information, and hides some activity.
3+
intro: 'A private profile displays only limited information, and hides some activity.'
44
versions:
55
fpt: '*'
66
topics:

‎content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ intro: 'You can manage how {% data variables.product.product_name %} looks to yo
44
versions:
55
fpt: '*'
66
ghae: '*'
7-
ghes: '>=3.2'
7+
ghes: '*'
88
ghec: '*'
99
topics:
1010
- Accounts

‎content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,11 @@ The repository owner has full control of the repository. In addition to the acti
4141
| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
4242
| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
4343
| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
44-
| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
45-
| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}
44+
| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
45+
| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
4646
| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
47-
| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %}
48-
| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
47+
| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
48+
| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
4949
| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
5050
| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
5151
| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
@@ -68,8 +68,8 @@ Collaborators can also perform the following actions.
6868

6969
| Action | More information |
7070
| :- | :- |
71-
| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
72-
| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %}
71+
| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
72+
| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
7373
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
7474
| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
7575
| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |

‎content/actions/automating-builds-and-tests/building-and-testing-net.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,6 @@ After a workflow completes, you can upload the resulting artifacts for analysis.
179179

180180
For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
181181

182-
183182
```yaml
184183
name: dotnet package
185184
@@ -225,10 +224,10 @@ on:
225224
226225
jobs:
227226
deploy:
228-
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
227+
runs-on: ubuntu-latest
229228
permissions:
230229
packages: write
231-
contents: read{% endif %}
230+
contents: read
232231
steps:
233232
- uses: {% data reusables.actions.action-checkout %}
234233
- uses: {% data reusables.actions.action-setup-dotnet %}

‎content/actions/automating-builds-and-tests/building-and-testing-ruby.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -279,10 +279,10 @@ on:
279279
jobs:
280280
build:
281281
name: Build + Publish
282-
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
282+
runs-on: ubuntu-latest
283283
permissions:
284284
packages: write
285-
contents: read{% endif %}
285+
contents: read
286286

287287
steps:
288288
- uses: {% data reusables.actions.action-checkout %}

‎content/actions/deployment/about-deployments/about-continuous-deployment.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ You can set up a {% data variables.product.prodname_actions %} workflow to deplo
2929

3030
You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
3131

32-
{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. {% endif %}For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
32+
{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
3333

3434
{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %}
3535

0 commit comments

Comments
 (0)