docs: fix a few small YAML typos (#763)
- Remove two extra colons that were making the yaml invalid 🕵️ - Add `yaml` tags to the markdown blocks 🧹
This commit is contained in:
parent
3539569fed
commit
a815c37614
14
README.md
14
README.md
|
|
@ -580,7 +580,7 @@ spec:
|
||||||
###### Example 2: Scale on each `pull_request` event against `develop` or `main` branches
|
###### Example 2: Scale on each `pull_request` event against `develop` or `main` branches
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
kind: RunnerDeployment:
|
kind: RunnerDeployment
|
||||||
metadata:
|
metadata:
|
||||||
name: myrunners
|
name: myrunners
|
||||||
spec:
|
spec:
|
||||||
|
|
@ -606,7 +606,7 @@ See ["activity types"](https://docs.github.com/en/actions/reference/events-that-
|
||||||
> This feature depends on an unreleased GitHub feature
|
> This feature depends on an unreleased GitHub feature
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
kind: RunnerDeployment:
|
kind: RunnerDeployment
|
||||||
metadata:
|
metadata:
|
||||||
name: myrunners
|
name: myrunners
|
||||||
spec:
|
spec:
|
||||||
|
|
@ -665,7 +665,7 @@ usually, this feature is used for following scenarios:
|
||||||
|
|
||||||
For the first scenario, you might consider configuration like the below:
|
For the first scenario, you might consider configuration like the below:
|
||||||
|
|
||||||
```
|
```yaml
|
||||||
apiVersion: actions.summerwind.dev/v1alpha1
|
apiVersion: actions.summerwind.dev/v1alpha1
|
||||||
kind: HorizontalRunnerAutoscaler
|
kind: HorizontalRunnerAutoscaler
|
||||||
metadata:
|
metadata:
|
||||||
|
|
@ -686,7 +686,7 @@ spec:
|
||||||
|
|
||||||
For the second scenario, you might consider something like the below:
|
For the second scenario, you might consider something like the below:
|
||||||
|
|
||||||
```
|
```yaml
|
||||||
apiVersion: actions.summerwind.dev/v1alpha1
|
apiVersion: actions.summerwind.dev/v1alpha1
|
||||||
kind: HorizontalRunnerAutoscaler
|
kind: HorizontalRunnerAutoscaler
|
||||||
metadata:
|
metadata:
|
||||||
|
|
@ -986,7 +986,7 @@ Note that there's no official Istio integration in actions-runner-controller. It
|
||||||
|
|
||||||
A basic `RunnerSet` would look like this:
|
A basic `RunnerSet` would look like this:
|
||||||
|
|
||||||
```
|
```yaml
|
||||||
apiVersion: actions.summerwind.dev/v1alpha1
|
apiVersion: actions.summerwind.dev/v1alpha1
|
||||||
kind: RunnerSet
|
kind: RunnerSet
|
||||||
metadata:
|
metadata:
|
||||||
|
|
@ -1018,7 +1018,7 @@ Similarly, container-related fields like resource requests and limits, container
|
||||||
|
|
||||||
For a more complex example, see the below:
|
For a more complex example, see the below:
|
||||||
|
|
||||||
```
|
```yaml
|
||||||
apiVersion: actions.summerwind.dev/v1alpha1
|
apiVersion: actions.summerwind.dev/v1alpha1
|
||||||
kind: RunnerSet
|
kind: RunnerSet
|
||||||
metadata:
|
metadata:
|
||||||
|
|
@ -1094,7 +1094,7 @@ GitHub seems to be adding an another flag called `--ephemeral` that is race-free
|
||||||
|
|
||||||
For example, a `RunnerSet` config with the flag enabled looks like:
|
For example, a `RunnerSet` config with the flag enabled looks like:
|
||||||
|
|
||||||
```
|
```yaml
|
||||||
kind: RunnerSet
|
kind: RunnerSet
|
||||||
metadata:
|
metadata:
|
||||||
name: example-runnerset
|
name: example-runnerset
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue