> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/vcontainer-registry/repository/repository-history.md).

# Repository History

Access the Repository to view information about the history of actions performed on the Repository, including:

* **User Name:** The agent directly interacting:
  * **Repository User:** The object directly interacting with the Image in the Repository.
  * **Default User:** Each GreenNode Account will have a corresponding Default-User used to initialize the Repository, create Repository Users, etc.
  * **Anonymous:** For actions on Public Repositories not through a Repository User.
* **Resource Name:** The name of the affected object, which can be Repository Name/Image Name.
* **Resource Type:** The affected objects include Repository/Image/Image Artifact.
* **Action Name:** The name of the action affecting the objects.
* **Action Time:** The time the action was performed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vngcloud.vn/vng-cloud-document/vcontainer-registry/repository/repository-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.