Fleet docs v0.2.0-rc.448

Projects

One row for each repo: open issues, open pull requests and the last 5 CI runs. Under the table, the waves of tickets with their progress.

How to read it

  • Repo, Issues (open), PRs (open).
  • CI: the last 5 runs, the newest at the left. Green ✓ passed, red ✕ failed, blue ↻ runs, yellow … waits, hollow – cancelled or skipped. Under them: the newest run, its name and age. Each badge links to its run.
  • Waves: "repo title · X of Y closed", a bar, and each ticket as ✓ (closed) or ○ (open).

Turn it on

Set dash.forgejo_api, dash.forgejo_token_file, dash.projects_dir, dash.profile.forgejo_host and dash.profile.forgejo_owner. Waves come from dash.profile.waves: {repo, first, end, title}. Only admins see this panel. It reads Forgejo only.

When it looks wrong

You see It means Do this
The table is empty No clone in projects_dir has an origin that contains forgejo_host, or forgejo_host is empty Set forgejo_host. Clone the repos into projects_dir.
"forgejo token: …" The token file cannot be read Fix forgejo_token_file and its mode
"HTTP 404 /repos/…" on a row The repo is not on Forgejo, or the token cannot read it Fix the origin or the token
"no commit id on repo/branch" The default branch has no commit, or a different name Check the default branch on Forgejo
"no runs" The repo has no CI runs Nothing
A red ✕ The last run failed Open the run from the badge

Code: fleet/internal/dash/projects.go.