Documentación Versión de la documentación: dev (Versión previa: Gitoodo aún no se ha publicado)

Para usuarios · Uso diario

Tablero

Partes de esta página aún no están disponibles en Español y se muestran en inglés.

En esta página
  1. En curso
  2. Issues
  3. Pull requests
  4. Versión
  5. Workers en vivo
  6. Agentes
  7. Control
Captura de la app: Tablero

El tablero muestra cada issue abierto con su estado, su puntuación y el agente que trabaja en él. La búsqueda y los filtros lo limitan a repositorios, estados o etiquetas.

  • Nuevo issue crea un issue, marcado como listo al instante si quieres.
  • Sesión de agente muestra en un terminal la sesión en curso de un agente.
  • Comentar en el chat pasa un issue al chat.

The board is split into subpages. In orchestrator mode they are In progress, Issues, Release, Agents and Control; in direct mode In progress, Issues and Pull requests. Gitoodo remembers the subpage you used last and opens it again. Clicking an issue anywhere on the board opens its details: repository, state, labels, priority, what it depends on, milestone, who works on it and, if it belongs to the next release, why.

En curso#

Lo que está en marcha, lo siguiente y lo atascado

In orchestrator mode this page answers "is everything moving?" at a glance. The line at the top says whether the orchestrator runs, is paused or cannot be reached; clicking it opens Control. Below it you see the Running workers (with Terminal to watch a running worker live; a note under them says how many are Left behind), the pull requests Ready to merge, the ready issues Up next in the order the dispatcher takes them (boosted issues first, then by score) and what is Stuck: issues that need a human, approval or clarification, and blocked, stalled or held ones. Click a stuck state or All to see exactly those issues under Issues.

In direct mode the page shows what needs you instead: how many questions wait in Asked of me, the counters Question open, Blocked, CI failing and Stale (a click filters the list under Issues), the recent throughput and a link to the open pull requests.

Issues#

Issues y pull requests por estado

Issues lists every issue and pull request of your switched-on repositories. In orchestrator mode they are grouped by repository: Search the board finds items by text, Filters narrow the list by repository, state or label, and Clear filters shows everything again. In a large window the list and the selected item's details sit side by side.

In orchestrator mode each row carries the actions that fit its state: Terminal for a running worker; Park, Restart or Stop to steer a worker (stopping and restarting ask first); Boost to move a ready issue to the front of the queue; and Control merge to hold or veto the pull request of an issue in review. In direct mode, Group by switches between Status, Repo, Account, Numbers (a table of counts; click a number to open the filtered list) and Needs you.

Pull requests#

Pull requests abiertos con comprobaciones y estado de fusión

Direct mode only: every open pull request of your repositories, grouped by repository. Each one shows whether its checks passed, failed (with the name of the first failing check), are running or are missing, whether it can be merged or has a conflict, and which issues it closes. Pull requests that need a look stand out, and In progress counts them. A click opens the pull request on the forge.

Versión#

Cuánto falta para la próxima versión en cada repositorio

La planificación de releases usa los hitos de la forja. Un issue entra en la próxima release con la etiqueta release:next, como dependencia de un issue de la release o con priority:p0.

Release status per repository shows how far each repository's next release is and what is still open in it. Copy summary copies the release plan as text; with Attach a link to Gitoodo it ends with a link to Gitoodo.

Workers en vivo#

Todos los workers en marcha, en vivo, aquí y en los equipos de workers

Cada mosaico muestra el terminal de un worker, en pequeño y en vivo. Abierto en grande empieza en modo solo lectura; solo «Tomar el control», tras una confirmación, envía tus teclas, el texto pegado y Ctrl-C al worker. Lo que se muestra pasa por la misma ocultación que los registros, así que los tokens conocidos nunca aparecen.

Agentes#

Quién trabaja en qué y qué se escribió en la forja

«Quedaron parados» son los issues cuya reserva caducó o que se marcaron como estancados sin que quede ningún worker en marcha; no cuentan como trabajo y, con «ready» en lugar de «stalled», vuelven a la cola.

Cada escritura en la forja, la más reciente primero

Running workers lists every issue that is really being worked on right now: first the workers this orchestrator runs (on this device or on a worker machine, named in the row), then issues another orchestrator holds with a reservation that is still valid. A reservation is valid while it has not expired and the issue is still in progress or in review. Once it has expired or the issue was flagged as stalled, the issue no longer counts as work and sits collapsed under Left behind; with “ready” instead of “stalled” it goes back into the queue. The overview's Workers tile counts the same workers and says how many run here, on a worker machine or on other machines. The row actions are the same as under Issues: Terminal opens the live terminal (macOS and Linux) and Detach leaves it while the worker keeps running; Park ends the worker and keeps the issue until a human decides, Restart starts it again in the same worktree, Stop ends it for good and hands the issue to a human.

Activity is the orchestrator's log of every write to the forge, newest first: which issue or pull request, what was written and why, marked OK or Failed. A click on the item opens it on the forge; Filter by repository narrows the log to one repository.

Control#

Pausar la automatización, retener fusiones, pausar repositorios

Orquestador activado/desactivado lo detiene todo: ni trabajo nuevo ni fusiones. Los agentes en marcha devuelven sus issues a la cola.

Retén o veta una pull request antes de que el orquestador la fusione. Una fusión automática ya activada en la forja no se puede retirar desde aquí.

Under Repositories you pause single repositories instead of the whole orchestrator: no new workers start there, running ones finish. Resume lets the repository take work again.

Versión de la documentación: dev