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: docs/methodology/renovate.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,6 @@ This guide explains how to use Pipeleak to discover and exploit common misconfig
15
15
There are two key points to understand:
16
16
17
17
1.**Code Execution by Renovated Repositories**
18
-
19
18
> Every project renovated by the same bot must be considered equally trusted and exposed to the same attack level. If one project is compromised, all others processed by that bot can be affected. Code execution by the renovated repository in the bot context is assumed in Renovate's threat model.
Long: "Generate Markdown documentation for all commands in this CLI application and mkdocs.yml. Must be run in an environment where 'mkdocs' is installed.",
15
+
Long: "Generates documentation for all commands. Must be run in an environment where 'mkdocs' is installed.",
16
16
Example: `
17
17
# Generate docs and serve them at http://localhost:8000
18
18
pipeleak docs --serve
@@ -26,7 +26,7 @@ pipeleak docs --serve
26
26
},
27
27
}
28
28
29
-
cmd.Flags().BoolVarP(&serve, "serve", "s", false, "Run 'mkdocs build' in the output folder after generating docs")
29
+
cmd.Flags().BoolVarP(&serve, "serve", "s", false, "Serve documentation after building")
30
30
cmd.Flags().BoolVarP(&githubPages, "github-pages", "g", false, "Build for GitHub Pages")
0 commit comments