added skip-driver-in-path argument to selenium_manager.en.md

[boris779]

User description

added documentation for the argument skip-driver-in-path

Description

Motivation and Context

I missed the documentation for that, needed for Problems with snap geckodriver

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Added documentation for the --skip-driver-in-path argument.

• Updated Selenium Manager documentation table with a new argument.

---

Changes walkthrough 📝

	Relevant files
Documentation	selenium_manager.en.md Added `--skip-driver-in-path` argument documentation          website_and_docs/content/documentation/selenium_manager.en.md Added a new row for --skip-driver-in-path argument in the arguments table. Described its purpose: avoiding drivers found in the PATH. +1/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	544aabe

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[shbenzer]

Thank you for the PR!

Could you please create an issue ticket describing this line: "needed for Problems with snap geckodriver"

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 10 rules

1. Duplicate argument row 🐞 Bug ≡ Correctness

Description

selenium_manager.en.md now lists --skip-driver-in-path twice in the arguments table (same
CLI/config/env values), which creates conflicting/duplicated documentation. Readers will see the
option twice and future edits may accidentally update only one entry.

Code

website_and_docs/content/documentation/selenium_manager.en.md[119]

+|`--skip-driver-in-path`|`skip-driver-in-path = true`|`SE_SKIP_DRIVER_IN_PATH=true`|Not using drivers found in the PATH|

Evidence

The table includes the newly added --skip-driver-in-path row and also already contains the same
--skip-driver-in-path row later (same config key and env var), proving this PR introduces a
duplicate entry.

website_and_docs/content/documentation/selenium_manager.en.md[112-132]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The Selenium Manager arguments table contains two identical entries for `--skip-driver-in-path` after this PR, which results in duplicate documentation.

### Issue Context
The PR adds a new row for `--skip-driver-in-path` near the top of the table, but the same argument is already documented later in the same table.

### Fix Focus Areas
- website_and_docs/content/documentation/selenium_manager.en.md[112-132]

### Suggested change
Remove one of the two `--skip-driver-in-path` rows (preferably the newly-added duplicate), and keep a single canonical entry with consistent formatting (e.g., `PATH` in backticks).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Duplicate argument row 🐞 Bug ≡ Correctness

selenium_manager.en.md now lists --skip-driver-in-path twice in the arguments table (same
CLI/config/env values), which creates conflicting/duplicated documentation. Readers will see the
option twice and future edits may accidentally update only one entry.

Agent Prompt

### Issue description
The Selenium Manager arguments table contains two identical entries for `--skip-driver-in-path` after this PR, which results in duplicate documentation.

### Issue Context
The PR adds a new row for `--skip-driver-in-path` near the top of the table, but the same argument is already documented later in the same table.

### Fix Focus Areas
- website_and_docs/content/documentation/selenium_manager.en.md[112-132]

### Suggested change
Remove one of the two `--skip-driver-in-path` rows (preferably the newly-added duplicate), and keep a single canonical entry with consistent formatting (e.g., `PATH` in backticks).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	f46c74b
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/6a5e10bb5836d00008dc6947
😎 Deploy Preview	https://deploy-preview-2254--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[diemol]

Thanks for this contribution, @boris779! After syncing this branch with trunk, it turns out the --skip-driver-in-path argument was independently documented in trunk back in August 2025 (commit 5c73d58, "Update Selenium Manager doc pages"), which also added the related --skip-browser-in-path entry. That means this PR's change is now fully superseded — the resulting diff against current trunk is empty, and merging as-is would have introduced a duplicate row in the arguments table (confirmed by the Qodo review bot on the latest commit).

Since the documentation gap this PR set out to fix is already covered, I'm closing it. Thanks again for flagging the gap and for the PR!