You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,8 +60,8 @@ jobs:
60
60
61
61
The actions are downloaded and run from the GitHub graph of repositories. The workflow references an action using a ref.
62
62
63
-
> **Note** Binding to a major version is the latest of that major version (e.g. `v2` = `2.*`)
64
-
>
63
+
> [!NOTE]
64
+
> Binding to a major version is the latest of that major version (e.g. `v2` = `2.*`)
65
65
> Major versions should guarantee compatibility. A major version can add net new capabilities but should not break existing input compatibility or break existing workflows.
66
66
67
67
```yml
@@ -72,7 +72,8 @@ The actions are downloaded and run from the GitHub graph of repositories. The wo
72
72
ocaml-compiler: ${{ matrix.ocaml-compiler }}
73
73
```
74
74
75
-
> **Warning** do not reference `master` since that is the latest code and can be carrying breaking changes of the next major version.
75
+
> [!WARNING]
76
+
> Do not reference `master` since that is the latest code and can be carrying breaking changes of the next major version.
76
77
77
78
Major version binding allows you to take advantage of bug fixes, critical functionality and security fixes. The `master` branch has the latest code and is unstable to bind to since changes get committed to the `master` and released by creating a tag.
78
79
@@ -106,7 +107,8 @@ steps:
106
107
107
108
The `ocaml-compiler` input supports the Semantic Versioning Specification, for more detailed examples please refer to the [documentation](https://github.com/npm/node-semver#ranges).
108
109
109
-
> **Note** With the naughty exception of `4.02.2`, point releases are meant to be strictly compatible, so once we (OCaml dev team) release a new point release, upgrading should be a no-brainer.
110
+
> [!NOTE]
111
+
> With the naughty exception of `4.02.2`, point releases are meant to be strictly compatible, so once we (OCaml dev team) release a new point release, upgrading should be a no-brainer.
110
112
111
113
Examples:
112
114
@@ -123,7 +125,8 @@ Consult the [examples](examples.md) page for more complex patterns.
123
125
124
126
**STATUS: EXPERIMENTAL**
125
127
126
-
Note: All extends are recommended to be used in separate jobs run on `ubuntu-latest`.
128
+
> [!NOTE]
129
+
> All extends are recommended to be used in separate jobs run on `ubuntu-latest`.
127
130
128
131
- [analysis](analysis)
129
132
- [deploy-doc](deploy-doc)
@@ -144,7 +147,8 @@ updates:
144
147
interval: weekly
145
148
```
146
149
147
-
> **Note** [Renovate](https://github.com/marketplace/renovate) is also available for free as a third-party tool, which is much more flexible than Dependabot - depending on the project and your preferences. If you just want to automate GitHub Actions updates, Dependabot is good enough.
150
+
> [!NOTE] \
151
+
> [Renovate](https://github.com/marketplace/renovate) is also available for free as a third-party tool, which is much more flexible than Dependabot - depending on the project and your preferences. If you just want to automate GitHub Actions updates, Dependabot is good enough.
0 commit comments