Skip to content

Docs deploy manual #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
afr1ka merged 2 commits into from
Jul 29, 2025
+2 −1
Merged

Docs deploy manual #136

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
91d9d21
add the manual trigger for docs build in actions
AnastasiaTWW Jul 29, 2025
a7a745d
trigger docs deploy
AnastasiaTWW Jul 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/documentation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ on:
- main
paths:
- 'docs/**'
workflow_dispatch:

permissions:
contents: write
Expand Down
2 changes: 1 addition & 1 deletion docs/configuration-guides/denylist-leaked-tokens.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ For REST API, should any of the flagged tokens surface in a request, the API Fir

To enable the denylist feature:

1. Draft a .txt file with the compromised tokens. Each token should be on a new line. Here is an example:
1. Draft a `.txt` file with the compromised tokens. Each token should be on a new line. Here is an example:

```txt
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzb21lIjoicGF5bG9hZDk5OTk5ODIifQ.CUq8iJ_LUzQMfDTvArpz6jUyK0Qyn7jZ9WCqE0xKTCA
Expand Down