From 235265014b6f13d83ea701243dd5ad6ec06c4913 Mon Sep 17 00:00:00 2001
From: Mohab Sameh <37941642+mohab-sameh@users.noreply.github.com>
Date: Mon, 26 Aug 2024 17:59:53 +0300
Subject: [PATCH] docs: add logs command (#1279)

---
 apps/docs/deploying-codemods/cli.mdx | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/apps/docs/deploying-codemods/cli.mdx b/apps/docs/deploying-codemods/cli.mdx
index c12998548..6b1aa2f20 100644
--- a/apps/docs/deploying-codemods/cli.mdx
+++ b/apps/docs/deploying-codemods/cli.mdx
@@ -300,9 +300,7 @@ codemod [codemod-name] --no-interactive
 
 </ResponseField>
 
-</ResponseField>
-
-<ResponseField name="--engine" type="boolean">
+<ResponseField name="--engine" type="string">
   Used to specify the engine for standalone codemod runs.
 
   <Note>When running standalone codemods (the ones that do not have a [codemod-compatible directory structure](/codemod-registry/introduction#required-codemod-package-structure)), you will be prompted to select a codemod engine that your codemod was built with. To support non-interactive mode, we added this optional flag.</Note>
@@ -330,6 +328,21 @@ codemod [codemod-name] -n [number-of-threads]
 ```
 </ResponseField>
 
+<ResponseField name="--log" type="boolean">
+  Can be used to generate a log file when running a codemod.
+
+```bash
+codemod [codemod-name] --logs
+```
+
+You can then open the log file by running:
+
+```bash
+codemod --logs
+```
+
+</ResponseField>
+
 ## Other commands
 
 <ResponseField name="codemod login">