> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/comentarios.md).

# Comments

It can be done, with the file selected in the list (right panel), in one of the following two ways: 1. From the “*Operations –> File -> Delete Signature”*

2. The context menu (right mouse button).

It allows both viewing existing comments and posting new ones.

When there are comments on the file, clicking this option will display a dialog like this one:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/i34JShB3CT1lcQ7Zlo2z/image1.png)

It contains the list of all comments that have been made about that file. Each one consists of the commenter's name, the date it was posted, and the text of the comment itself.

From here, the user can modify and/or delete any comments they authored.

By clicking the “Publish” button, or if up to that moment there has been no comment on the file, the dialog that will open will be this one:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/2VLBAG3nX1UTDhO90Xit/image2.png)

Comments are stored signed, and each time they are consulted their integrity is checked.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/PDQ6GYVMcnHKcOmDW62d/image3.png)

When there are comments on a file, in the aforementioned lists an icon of a document appears under the “Commented by…” column, followed by the names of the users, separated by “;”, who made them. The asterisk next to the name indicates that the user is the one logged in.


---

# 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.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/comentarios.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.