You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Action required if your config binds s in the shell context.s now
opens the store picker, and a config that already binds it to another shell
action fails startup with key "s" conflicts between actions ... in shell context. Rebind one of the two; docs/user-guide/key-bindings.md
has an example.
Added: a store picker.s from any tab lists every central task store
registered on this machine with its name, project path and health, and marks
the one in use. enter switches the running app to the highlighted store in
place: the board, Docs tab, search, detail and launchers all follow, and the
header names the new store. A store the registry knows but cannot open stays
listed with the reason. esc returns to the tab you came from.
Changed: starting with no task store opens the picker instead of exiting. taskmgr-ui run outside any project used to print no .tasks directory found
and exit 1. It now opens on the picker with a toast saying why, as does an
unknown --store-name. A store that exists but cannot be opened still exits
1.
Added: create a store from the picker. When started somewhere with no
store, two rows above the registry offer to create a local store or a central
store for that directory, with the ID prefix and registry name prefilled the
way taskmgr init would choose them. The new store opens straight away.
Changed: launchers are refused while the active store's project directory
is missing. A central store whose project was moved or deleted still opens,
but n, p and l used to run in a directory that was gone and blamed the
launcher. Each now refuses with a toast naming the path, and the Detail
footer says the launchers are off. A launcher with its own workdir still
runs; e is unaffected.
Columns now read newest change first. Not Ready, Ready, In Progress and
the Docs tab order their rows by last change, most recent at the top, with
priority as the tie-break. Before, priority came first and a P0 issue
untouched for a month sat above the work you changed an hour ago. Done keeps
its close-date order.
Age markers show where the stale work starts. A muted divider reading older than 1 day and another reading older than 1 week sit before the
first issue past that age, each with the count of issues below it. A column
of fresh work shows no divider; a column where everything is stale shows
both stacked at the top. Done draws none.
Fixed: a write that a store hook refused was reported as update issue failed: update issue: unknown: ..., as if the app had faulted.
It is now reported as a refusal with the hook's own reason, the way the taskmgr CLI reports it.
Fixed: under --repo memory, a search page shorter than the full result set
was reported as complete, so no further page was offered and the list was
silently truncated.