Skip to content

Commit f272eec

Browse files
sarahsmattpollard
andauthored
Remove deprecated GHES versions from content and data (github#15830)
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script) * package-lock * turn elsif into two ifs to prepare for running Liquid deprecation script * ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.) * ran script/remove-deprecated-enterprise-version-markup.js --release 2.15 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.17 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.18 * update hardcoded test * Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21 Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
1 parent dc5b6f2 commit f272eec

355 files changed

Lines changed: 346 additions & 566 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
-2.87 KB
Binary file not shown.
-4.27 KB
Binary file not shown.
-7.89 KB
Binary file not shown.

‎content/actions/creating-actions/metadata-syntax-for-github-actions.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ Action metadata files use YAML syntax. If you're new to YAML, you can read "[Lea
4242

4343
This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
4444

45-
4645
```yaml
4746
inputs:
4847
numOctocats:
@@ -54,7 +53,6 @@ inputs:
5453
required: true
5554
```
5655
57-
5856
When you specify an input to an action in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
5957

6058
For example, if a workflow defined the numOctocats and octocatEyeColor inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables.

‎content/actions/reference/events-that-trigger-workflows.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -602,7 +602,7 @@ Runs your workflow anytime the `release` event occurs. {% data reusables.develop
602602

603603
| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
604604
| --------------------- | -------------- | ------------ | -------------|
605-
| [`release`](/webhooks/event-payloads/#release) | - `published`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released`{% endif %} | Last commit in the tagged release | Tag of release |
605+
| [`release`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag of release |
606606

607607
{% data reusables.developer-site.limit_workflow_to_activity_types %}
608608

‎content/actions/reference/workflow-commands-for-github-actions.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -274,7 +274,6 @@ steps:
274274
echo 'EOF' >> $GITHUB_ENV
275275
```
276276

277-
278277
### Adding a system path
279278

280279
`echo "{path}" >> $GITHUB_PATH`

‎content/actions/reference/workflow-syntax-for-github-actions.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -704,7 +704,6 @@ The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you
704704
1. Use defaults that allow using the action without specifying any `args`.
705705
1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting.
706706

707-
708707
#### **`jobs.<job_id>.steps.with.entrypoint`**
709708

710709
Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
@@ -839,7 +838,6 @@ strategy:
839838

840839
You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job.
841840

842-
843841
{% raw %}
844842
```yaml
845843
runs-on: ${{ matrix.os }}

‎content/admin/configuration/command-line-utilities.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,15 +180,13 @@ This utility allows you to control the state of the installation's maintenance m
180180
ghe-maintenance -h
181181
```
182182

183-
{% if currentVersion ver_gt "enterprise-server@2.17" %}
184183
#### ghe-motd
185184

186185
This utility re-displays the message of the day (MOTD) that administrators see when accessing the instance via the administrative shell. The output contains an overview of the instance's state.
187186

188187
```shell
189188
ghe-motd
190189
```
191-
{% endif %}
192190

193191
#### ghe-nwo
194192

‎content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,7 @@ Enabling {% data variables.product.prodname_github_connect %} also creates a {%
3737

3838
Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.prodname_ghe_server %}.
3939

40-
{% if currentVersion ver_gt "enterprise-server@2.18" %}
4140
For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)."
42-
{% endif %}
4341
### Enabling {% data variables.product.prodname_github_connect %}
4442

4543
1. Sign in to {% data variables.product.product_location_enterprise %} and {% data variables.product.prodname_dotcom_the_website %}.

‎content/admin/enterprise-management/about-geo-replication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/
1818

1919
### Limitations
2020

21-
Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes are limited by the slowest replica{% if currentVersion ver_gt "enterprise-server@2.17" %}, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary{% endif %}. Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests.
21+
Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes are limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests.
2222

2323
### Monitoring a geo-replication configuration
2424

0 commit comments

Comments
 (0)