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
@@ -63,7 +63,7 @@ git fetch origin tag 1.0.1-0 --no-tags --shallow-exclude=1.0.0-0 # This will fet
63
63
64
64
## Security Rules 🔐
65
65
1. Do **not** use `pull_request_target` trigger unless an external fork needs access to secrets, or a _write_ `GITHUB_TOKEN`.
66
-
1. Do **not ever** write a `pull_request_target` trigger with an explicit PR checkout, e.g. using `actions/checkout@v4`. This is [discussed further here](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)
66
+
1. Do **not ever** write a `pull_request_target` trigger with an explicit PR checkout, e.g. using `useblacksmith/checkout@c9796daa2a4bdebdab5bd16be2c09a70cd4e1121`. This is [discussed further here](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)
67
67
1. **Do use** the `pull_request` trigger as it does not send internal secrets and only grants a _read_ `GITHUB_TOKEN`.
68
68
1. If an untrusted (i.e: not maintained by GitHub) external action needs access to any secret (`GITHUB_TOKEN` or internal secret), use the commit hash of the workflow to prevent a modification of underlying source code at that version. For example:
69
69
1. **Bad:** `hmarr/auto-approve-action@v2.0.0` Relies on the tag
@@ -138,7 +138,7 @@ In order to bundle actions with their dependencies into a single Node.js executa
138
138
### Important tips about creating GitHub Actions
139
139
140
140
- When calling your GitHub Action from one of our workflows, you must:
141
-
- First call `@actions/checkout`.
141
+
- First call `useblacksmith/checkout@c9796daa2a4bdebdab5bd16be2c09a70cd4e1121` (`# v1`).
142
142
- Use the relative path of the action in GitHub from the root of this repo, like so:
0 commit comments