tui: just run-tui recipe & Forgejo Actions CI integration #44

New issue

Closed

opened 2026-04-11 13:07:02 +00:00 by charles · 0 comments

charles commented

2026-04-11 13:07:02 +00:00

Owner

User story

As a developer working on loom-tui, I want a one-liner to run it in debug mode and CI coverage on every push, so that local iteration and regression detection are frictionless.

Acceptance criteria

justfile

just run-tui — runs cargo run -p loom-tui with RUST_LOG=loom=debug,loom_tui=debug
just build-tui — cargo build -p loom-tui
Existing just qa continues to cover the new crate (fmt, clippy, test -p all)

Forgejo CI

.forgejo/workflows/qa.yml remains single qa job; verify it picks up loom-tui automatically because it already targets the workspace
If the qa job currently filters features or skips crates, ensure loom-tui is not skipped
Release workflow (release.yml) builds the loom-tui binary for x86_64 and aarch64 and uploads it under a dedicated artifact (loom-tui-{VERSION}-{ARCH}-linux.tar.gz)

Docs

README / CLAUDE.md gains a line about just run-tui

Tests

N/A at the ticket level; this ticket is verified green by CI running cargo test -p loom-tui

Out of scope

Packaging (nfpm, PKGBUILD, meson) — separate ticket
Unit / integration tests themselves — separate test ticket

References

Spec §9 "Testing Requirements"
Spec §11 "Build & Packaging"

## User story As a developer working on loom-tui, I want a one-liner to run it in debug mode and CI coverage on every push, so that local iteration and regression detection are frictionless. ## Acceptance criteria ### justfile - [ ] `just run-tui` — runs `cargo run -p loom-tui` with `RUST_LOG=loom=debug,loom_tui=debug` - [ ] `just build-tui` — `cargo build -p loom-tui` - [ ] Existing `just qa` continues to cover the new crate (`fmt`, `clippy`, `test` -p all) ### Forgejo CI - [ ] `.forgejo/workflows/qa.yml` remains single `qa` job; verify it picks up `loom-tui` automatically because it already targets the workspace - [ ] If the qa job currently filters features or skips crates, ensure `loom-tui` is not skipped - [ ] Release workflow (`release.yml`) builds the `loom-tui` binary for x86_64 and aarch64 and uploads it under a dedicated artifact (`loom-tui-{VERSION}-{ARCH}-linux.tar.gz`) ### Docs - [ ] README / CLAUDE.md gains a line about `just run-tui` ### Tests - [ ] N/A at the ticket level; this ticket is verified green by CI running `cargo test -p loom-tui` ## Out of scope - Packaging (nfpm, PKGBUILD, meson) — separate ticket - Unit / integration tests themselves — separate test ticket ## References - Spec §9 "Testing Requirements" - Spec §11 "Build & Packaging"

charles added this to the loom-tui v0.1.0 milestone

2026-04-11 13:07:02 +00:00

charles added the

type:user-story

area:infra

labels

2026-04-11 13:07:02 +00:00

charles referenced this issue

2026-04-11 13:07:50 +00:00

tui: tracking — loom-tui v0.1.0 roadmap & implementation order #47

charles referenced this issue

2026-04-11 15:22:44 +00:00