New run: one page with recent repositories, and nothing asked twice #541

Closed
opened 2026-11-15 11:49:48 -05:00 by cmoriarty · 1 comment
Owner

What happens
New run shows one question at a time, opens on an empty repository field, and asks whether to introduce git flow and OpenSpec on every run, even after a no.

What we want
The Sheet layout of the mock below: one page of labelled rows, like Settings.

  • Recent repositories first, each with its last run; a search for the rest; New project beside them.
  • Every option already has a value, and Start run is always on screen.
  • Git flow is a switch that each repository keeps from its last run. OpenSpec follows the pipeline: the page says "adds OpenSpec" only when the run would add it.

This takes the recent-repositories part of #361. Batches and suggested issues stay there.

Done when

  • A run started from the page sends what the wizard sends today for the same choices.
  • A repository's next run starts with its last run's git flow, and nothing is asked.
  • The page fits a phone.

The Sheet layout, at desktop width

Where to look: ui/src/components/NewRun.tsx, ui/src/lib/methodology.ts, repo_profile in src/osf/api/hooks.py.

From the New run mock of 2026-11-14. The Sheet layout was chosen on 11-15.

**What happens** New run shows one question at a time, opens on an empty repository field, and asks whether to introduce git flow and OpenSpec on every run, even after a no. **What we want** The Sheet layout of the mock below: one page of labelled rows, like Settings. - Recent repositories first, each with its last run; a search for the rest; New project beside them. - Every option already has a value, and Start run is always on screen. - Git flow is a switch that each repository keeps from its last run. OpenSpec follows the pipeline: the page says "adds OpenSpec" only when the run would add it. This takes the recent-repositories part of #361. Batches and suggested issues stay there. **Done when** - A run started from the page sends what the wizard sends today for the same choices. - A repository's next run starts with its last run's git flow, and nothing is asked. - The page fits a phone. ![The Sheet layout, at desktop width](/attachments/bd6c59e8-3057-4133-80ba-e68172fde9ba) Where to look: `ui/src/components/NewRun.tsx`, `ui/src/lib/methodology.ts`, `repo_profile` in `src/osf/api/hooks.py`. *From the New run mock of 2026-11-14. The Sheet layout was chosen on 11-15.*
Author
Owner

Shipped in #544, archived in #545.

  • New run is one page of rows in the Sheet layout. Every row starts with a value, Start run stays on screen and says what is missing, and ⌘↵ starts the run.
  • Recent repositories first: the repositories of the newest runs, archived ones included. A search covers all of Forgejo, and New project sits beside it.
  • No questions: OpenSpec follows the pipeline (adds OpenSpec), and Git flow is a switch (creates develop from main).
  • Memory: a repository brings its newest run's git flow (last_git_flow on /api/repo-profile) and its last tests. It starts on quick-fix without OpenSpec.
  • Start run sends what the wizard sent for the same choices.

Evidence, from the laptop:

  • tests/api/test_repo_profile.py failed before last_git_flow existed, and passes.
  • The three New run journeys fail on main's console and pass.
  • The archived-runs case failed without its read.
  • ./tools/test.sh is green.
  • The page was tried on production's data at 1440 and 390 px.

Not in it:

  • The pipeline is not remembered per repository: it belongs to the work.
  • Deleting a run deletes its events, so a deleted run's repository and its git flow choice are gone. Filling the list from Forgejo was offered and not taken.
**Shipped** in #544, archived in #545. - New run is one page of rows in the Sheet layout. Every row starts with a value, Start run stays on screen and says what is missing, and ⌘↵ starts the run. - **Recent repositories first:** the repositories of the newest runs, archived ones included. A search covers all of Forgejo, and New project sits beside it. - **No questions:** OpenSpec follows the pipeline (`adds OpenSpec`), and Git flow is a switch (`creates develop from main`). - **Memory:** a repository brings its newest run's git flow (`last_git_flow` on `/api/repo-profile`) and its last tests. It starts on `quick-fix` without OpenSpec. - Start run sends what the wizard sent for the same choices. **Evidence, from the laptop:** - `tests/api/test_repo_profile.py` failed before `last_git_flow` existed, and passes. - The three New run journeys fail on main's console and pass. - The archived-runs case failed without its read. - `./tools/test.sh` is green. - The page was tried on production's data at 1440 and 390 px. **Not in it:** - The pipeline is not remembered per repository: it belongs to the work. - Deleting a run deletes its events, so a deleted run's repository and its git flow choice are gone. Filling the list from Forgejo was offered and not taken.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#541
No description provided.