Skip to content

Commit 637917e

Browse files
committed
README: re-add "pro tip" language
Signed-off-by: William Woodruff <[email protected]>
1 parent 4864f13 commit 637917e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,8 @@ jobs:
6363
```
6464
6565
> [!NOTE]
66-
> Instead of using branch pointers, like `unstable/v1`, pin versions of Actions
67-
> that you use to tagged versions or sha1 commit identifiers.
66+
> Pro tip: instead of using branch pointers, like `unstable/v1`, pin versions of
67+
> Actions that you use to tagged versions or sha1 commit identifiers.
6868
> This will make your workflows more secure and better reproducible, saving you
6969
> from sudden and unpleasant surprises.
7070

@@ -79,7 +79,7 @@ Other indices that support trusted publishing can also be used, like TestPyPI:
7979
_(don't forget to update the environment name to `testpypi` or similar!)_
8080

8181
> [!NOTE]
82-
> Only set the `id-token: write` permission in the job that does
82+
> Pro tip: only set the `id-token: write` permission in the job that does
8383
> publishing, not globally. Also, try to separate building from publishing
8484
> — this makes sure that any scripts maliciously injected into the build
8585
> or test environment won't be able to elevate privileges while flying under
@@ -192,7 +192,7 @@ default) setting as follows:
192192
```
193193

194194
> [!NOTE]
195-
> Try to avoid enabling this setting where possible. If you
195+
> Pro tip: try to avoid enabling this setting where possible. If you
196196
> have steps for publishing to both PyPI and TestPyPI, consider only using
197197
> it for the latter, having the former fail loudly on duplicates.
198198

0 commit comments

Comments
 (0)