> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-zh/action-shi-yong-zhi-nan/file-and-folder/move-rename-folder.md).

# Move / rename folder

Move / rename folder 是一个多功能的操作,用于将整个文件夹(包括其内部的所有文件和子文件夹)移动到新位置,或在硬盘上的当前位置直接重命名该文件夹。

与文件操作类似,此操作会将文件夹完全剪切到新位置(如果是移动)或完全替换旧名称(如果是重命名)。

🎥 查看更多教程视频:[点击这里](https://youtu.be/EH7olDLAb9c)。

#### 配置参数:

* Source Folder:需要移动或重命名的源文件夹的绝对路径(例如:`D:\GPM_Data\old_name`)。
* Destination Folder:移动到的目标文件夹的绝对路径,或重命名后包含新文件夹名称的路径(例如:`E:\Backup_Data\old_name` 或 `D:\GPM_Data\new_name`)。

#### 实际示例 1:重命名文件夹(Rename)

您有一个存放临时数据的文件夹,名为 `temp_data`。当脚本处理完其内部的所有数据后,您想将该文件夹重命名为 `processed_data`,以标记完成状态。

* Source Folder:`D:\GPM_Data\temp_data`
* Destination Folder:`D:\GPM_Data\processed_data` *(保持父路径不变,仅更改末尾的文件夹名称)*。
* 结果:`temp_data` 文件夹将立即被重命名为 `processed_data`。

<figure><img src="https://1806980278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiDNNiVZHPKSIcyshmOTB%2Fuploads%2Fgit-blob-bd1a0334169f38ef5d7cba01409b30c024079a32%2Fff-15.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gpmautomate.com/automate-zh/action-shi-yong-zhi-nan/file-and-folder/move-rename-folder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
