# Page Not Found

The URL `es/bits/Cambiar-la-URL-remota-de-un-repositorio-Git` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Ejecutar un pod con imágenes de un repositorio privado](https://dojo.lkmx.io/kubernetes/ejecutar-un-pod-con-imagenes-de-un-repositorio-privado.md)
- [Cambiar el formato de un video en HandBrake](https://dojo.lkmx.io/editor-de-video/handbrake/cambiar-el-formato-de-un-video-en-handbrake.md)
- [Ver gráfico del repositorio](https://dojo.lkmx.io/git-graph/ver-grafico-del-repositorio.md)
- [Crear un repositorio en GitLab](https://dojo.lkmx.io/gitlab/crear-un-repositorio-en-gitlab.md)
- [Implementar un contrato NFT](https://dojo.lkmx.io/tezos/implementar-un-contrato-nft.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

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

```
GET https://dojo.lkmx.io/kubernetes/ejecutar-un-pod-con-imagenes-de-un-repositorio-privado.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.

### Option 2 — Browse the documentation index

Full index: https://dojo.lkmx.io/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://dojo.lkmx.io/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/kubernetes/ejecutar-un-pod-con-imagenes-de-un-repositorio-privado.md`).

You may also use `Accept: text/markdown` header for content negotiation.