docs: remove trailing newlines in code blocks (#27990)
This commit is contained in:
@@ -404,7 +404,6 @@ For example, you can run a workflow when the `checks_requested` activity has occ
|
|||||||
on:
|
on:
|
||||||
merge_group:
|
merge_group:
|
||||||
types: [checks_requested]
|
types: [checks_requested]
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|||||||
@@ -208,7 +208,6 @@ This utility lists repositories on your appliance that use {% data variables.pro
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
ghe-legacy-github-services-report
|
ghe-legacy-github-services-report
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
### ghe-logs-tail
|
### ghe-logs-tail
|
||||||
|
|||||||
@@ -350,7 +350,6 @@ CLI:
|
|||||||
script: 'echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
script: 'echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
|
||||||
--ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
|
--ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
|
||||||
--sarif=/temp/example-repo-csharp.sarif --github-auth-stdin'
|
--sarif=/temp/example-repo-csharp.sarif --github-auth-stdin'
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
### Multiple languages using autobuild (C++, Python)
|
### Multiple languages using autobuild (C++, Python)
|
||||||
|
|||||||
@@ -470,7 +470,6 @@ updates:
|
|||||||
- ruby-github # only access to registries associated with this ecosystem/directory
|
- ruby-github # only access to registries associated with this ecosystem/directory
|
||||||
schedule:
|
schedule:
|
||||||
interval: "monthly"
|
interval: "monthly"
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
|
|||||||
@@ -38,7 +38,6 @@ Scala | [Sbt Dependency Submission](https://github.com/marketplace/actions/sbt-d
|
|||||||
For example, the following [Go Dependency Submission](https://github.com/actions/go-dependency-submission) workflow calculates the dependencies for a Go build-target (a Go file with a `main` function) and submits the list to the Dependency submission API.
|
For example, the following [Go Dependency Submission](https://github.com/actions/go-dependency-submission) workflow calculates the dependencies for a Go build-target (a Go file with a `main` function) and submits the list to the Dependency submission API.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
|
|
||||||
name: Go Dependency Submission
|
name: Go Dependency Submission
|
||||||
on:
|
on:
|
||||||
push:
|
push:
|
||||||
@@ -77,7 +76,6 @@ jobs:
|
|||||||
# used by all build targets for the module. This may
|
# used by all build targets for the module. This may
|
||||||
# include Go dependencies used by tests and tooling.
|
# include Go dependencies used by tests and tooling.
|
||||||
go-build-target: go-example/cmd/octocat.go
|
go-build-target: go-example/cmd/octocat.go
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
### Creating your own action
|
### Creating your own action
|
||||||
|
|||||||
@@ -84,7 +84,6 @@ The default development container, or "dev container," for {% data variables.pro
|
|||||||
// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
|
// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
|
||||||
// "remoteUser": "root"
|
// "remoteUser": "root"
|
||||||
}
|
}
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
{% data reusables.codespaces.devcontainer-properties-1 %}
|
{% data reusables.codespaces.devcontainer-properties-1 %}
|
||||||
|
|||||||
@@ -187,7 +187,6 @@ jobs:
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
}' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
|
}' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
## Example workflow authenticating with a {% data variables.product.pat_generic %}
|
## Example workflow authenticating with a {% data variables.product.pat_generic %}
|
||||||
|
|||||||
@@ -48,7 +48,6 @@ query(
|
|||||||
id
|
id
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
{% data reusables.enterprise_migrations.retreive-enterprise-id-graphql %}
|
{% data reusables.enterprise_migrations.retreive-enterprise-id-graphql %}
|
||||||
|
|||||||
@@ -35,7 +35,6 @@ jobs:
|
|||||||
uses: actions/hello-world-javascript-action@main
|
uses: actions/hello-world-javascript-action@main
|
||||||
with:
|
with:
|
||||||
who-to-greet: ${{ vars.GREET_NAME }}
|
who-to-greet: ${{ vars.GREET_NAME }}
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
|
|||||||
@@ -25,5 +25,4 @@ jobs:
|
|||||||
datacenter: "site-a"
|
datacenter: "site-a"
|
||||||
- site: "staging"
|
- site: "staging"
|
||||||
datacenter: "site-b"
|
datacenter: "site-b"
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -54,5 +54,4 @@ body:
|
|||||||
value: |
|
value: |
|
||||||
### The thrilling conclusion
|
### The thrilling conclusion
|
||||||
_to our template_
|
_to our template_
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -7,7 +7,6 @@ on:
|
|||||||
schedule:
|
schedule:
|
||||||
# * is a special character in YAML so you have to quote this string
|
# * is a special character in YAML so you have to quote this string
|
||||||
- cron: '30 5,17 * * *'
|
- cron: '30 5,17 * * *'
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
A single workflow can be triggered by multiple `schedule` events. You can access the schedule event that triggered the workflow through the `github.event.schedule` context. This example triggers the workflow to run at 5:30 UTC every Monday-Thursday, but skips the `Not on Monday or Wednesday` step on Monday and Wednesday.
|
A single workflow can be triggered by multiple `schedule` events. You can access the schedule event that triggered the workflow through the `github.event.schedule` context. This example triggers the workflow to run at 5:30 UTC every Monday-Thursday, but skips the `Not on Monday or Wednesday` step on Monday and Wednesday.
|
||||||
|
|||||||
Reference in New Issue
Block a user