Skip to content

Instantly share code, notes, and snippets.

@vlad-ko
Last active May 7, 2025 15:28
Show Gist options
  • Save vlad-ko/e2b2c0e71734513325d85354d7c78b7f to your computer and use it in GitHub Desktop.
Save vlad-ko/e2b2c0e71734513325d85354d7c78b7f to your computer and use it in GitHub Desktop.
### 🔧 **Instructions for Running CLI and Validating Network Coverage**
1. **Run the CLI with Required Flags**
Execute the CLI using the same arguments as before, making sure to include:
* `--dry-run`
* `--slug`
* `--sha`
* `--git-service`
2. **Locate the Output**
* The output will be saved to a file named `coverage_report.txt`.
* Upload this file to the shared Google Drive.
* ⚠️ Note: This file **only contains the network section**, not the full coverage report.
3. **Check Console Logs for Network Files**
In the console output, look for log lines like these:
```
debug - 2025-05-06 22:46:43,538 -- Network Files Sample: [...]
debug - 2025-05-06 22:46:43,538 -- Total network files: 14
```
* The number after `Total network files:` should be **greater than 0**.
* ✅ If it is, that's a good sign — open `coverage_report.txt` and verify the contents look reasonable.
4. **Confirm the Working Directory**
Look for this log entry:
```
debug - 2025-05-06 22:46:43,498 -- NetworkFinder.find_files --- { ..., "network_root_folder": "/path/to/your/project", ... }
```
* You’re specifically looking for the `network_root_folder` field.
* This tells you **which directory the CLI searched for network-relevant files**.
5. **Troubleshooting Incorrect Directory**
* If the `network_root_folder` is **incorrect**:
* Try running the CLI from the correct project directory.
* Then, re-check that `coverage_report.txt` is accurate.
* Alternatively, use the `--network-root-folder` flag to explicitly set the correct directory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment