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: learn-pr/github/manage-github-actions-enterprise/includes/manage-encrypted-secrets.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,7 +154,7 @@ Security hardening for GitHub Actions plays a role in keeping your software supp
154
154
155
155
Some best practices for mitigating script injection attacks on GitHub actions include:
156
156
157
-
1. *Use Javascript actions instead of inline scripts*: Use JavaScript actions that accept context values as arguments instead of embedding those values in inline scripts. This approach reduces the risk of script injection because the context data is not used to generate or execute shell commands directly.
157
+
1. *Use Javascript actions instead of inline scripts*: Use Javascript actions that accept context values as arguments instead of embedding those values in inline scripts. This approach reduces the risk of script injection because the context data is not used to generate or execute shell commands directly.
158
158
159
159
Passing a variable as an input to a JavaScript action helps prevent it from being used in a script injection attack.
160
160
@@ -523,7 +523,7 @@ Many enterprises integrate GitHub Actions with external secret management soluti
0 commit comments