[PR #421] [MERGED] Fix directory path in README after cloning #429

New issue

Closed

opened 2026-02-26 12:41:21 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:41:21 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE-Local/pull/421
Author: @zeosamaster
Created: 12/30/2025
Status: ✅ Merged
Merged: 12/30/2025
Merged by: @tremor021

Base: main ← Head: patch-1

📝 Commits (1)

ee14b89 Fix directory path in README after cloning

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 README.md (+1 -1)

📄 Description

✍️ Description

Update the path used on Install steps after cloning the repo

Link: #

✅ Prerequisites (X in brackets)

Self-review completed – Code follows project standards.
Tested thoroughly – Changes work as expected.
No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

Screenshot for frontend Change

N/A

🛠️ Type of Change (X in brackets)

🐞 Bug fix – Resolves an issue without breaking functionality.
✨ New feature – Adds new, non-breaking functionality.
💥 Breaking change – Alters existing functionality in a way that may require updates.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE-Local/pull/421 **Author:** [@zeosamaster](https://github.com/zeosamaster) **Created:** 12/30/2025 **Status:** ✅ Merged **Merged:** 12/30/2025 **Merged by:** [@tremor021](https://github.com/tremor021) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`ee14b89`](https://github.com/community-scripts/ProxmoxVE-Local/commit/ee14b89868cd9e8c41c0aaab9941d3180fec983e) Fix directory path in README after cloning ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) </details> ### 📄 Description  ## ✍️ Description Update the path used on Install steps after cloning the repo ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [X] **Self-review completed** – Code follows project standards. - [X] **Tested thoroughly** – Changes work as expected. - [X] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. ## Screenshot for frontend Change N/A ## 🛠️ Type of Change (**X** in brackets) - [X] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>