Skip to content

Commit f5a17d0

Browse files
GrantBirkiCopilot
andauthored
Update docs/deployment-confirmation.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 7d3da65 commit f5a17d0

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/deployment-confirmation.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ For projects that require the highest level of deployment safety/security, the b
66

77
This can be considered a "final safety check" before a deployment can continue.
88

9-
By using this feature, it is also an extremely effect way to prevent accidental or malicious commits from being deployed without first having one last safety review. This is important for hardening against Actions related [TOCTOU](https://github.com/AdnaneKhan/ActionsTOCTOU) vulnerabilities.
10-
9+
By using this feature, it is also an extremely effective way to prevent accidental or malicious commits from being deployed without first having one last safety review. This is important for hardening against Actions related [TOCTOU](https://github.com/AdnaneKhan/ActionsTOCTOU) vulnerabilities.
1110
## How it works
1211

1312
When a user invokes a deployment via the `.deploy` (or `.noop`) command, the branch-deploy Action will pause _just_ before the final call to start a deployment by this Action. The Action will then create a new comment on the pull request that invoked the deployment, asking the user to confirm (or reject) the deployment.

0 commit comments

Comments
 (0)