Skip to content

Commit 278e38f

Browse files
author
Sarah Edwards
authored
Revert "[April 13] serialization feature doc (#18606)" (#18739)
This reverts commit 2c881b6.
1 parent 16cdd98 commit 278e38f

4 files changed

Lines changed: 2 additions & 67 deletions

File tree

content/actions/reference/environments.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,6 @@ For more information on syntax to reference environments in workflows, see "[Wor
7171

7272
When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
7373

74-
### Using concurrency to serialize deployments in an environment
75-
You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#concurrency)."
76-
7774
### Deleting an environment
7875

7976
{% data reusables.github-actions.permissions-statement-environment %}

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

Lines changed: 2 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -221,18 +221,6 @@ defaults:
221221
working-directory: scripts
222222
```
223223

224-
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
225-
### `concurrency`
226-
227-
{% data reusables.actions.concurrency-beta %}
228-
229-
Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the `github` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
230-
231-
You can also specify `concurrency` at the job level. For more information, see [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
232-
233-
{% data reusables.actions.actions-group-concurrency %}
234-
235-
{% endif %}
236224
### `jobs`
237225

238226
A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs.<job_id>.needs` keyword.
@@ -356,14 +344,13 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
356344

357345
The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)."
358346

359-
You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. We support [context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions) only when you provide the environment object. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
347+
You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
360348

361349
##### Example using a single environment name
362-
{% raw %}
350+
363351
```yaml
364352
environment: staging_environment
365353
```
366-
{% endraw %}
367354

368355
##### Example using environment name and URL
369356

@@ -385,25 +372,6 @@ environment:
385372
{% endraw %}
386373
{% endif %}
387374

388-
389-
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
390-
### `jobs.<job_id>.concurrency`
391-
392-
{% data reusables.actions.concurrency-beta %}
393-
394-
{% note %}
395-
396-
**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other.
397-
398-
{% endnote %}
399-
400-
Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
401-
402-
You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
403-
404-
{% data reusables.actions.actions-group-concurrency %}
405-
406-
{% endif %}
407375
### `jobs.<job_id>.outputs`
408376

409377
A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs.<job_id>.needs`](#jobsjob_idneeds).

data/reusables/actions/actions-group-concurrency.md

Lines changed: 0 additions & 25 deletions
This file was deleted.

data/reusables/actions/concurrency-beta.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

0 commit comments

Comments
 (0)