Skip to content

Release 0.9.0 new flow - #13

Merged
grinev merged 16 commits into
mainfrom
release-0.9.0-new-flow
Sep 2, 2026
Merged

grinev merged 16 commits into
mainfrom
release-0.9.0-new-flow

Conversation

@grinev

@grinev grinev commented Sep 2, 2026

Copy link
Copy Markdown
Owner

No description provided.

grinev and others added 16 commits August 27, 2026 19:06
Both tasks now carry a spec field pointing at their product spec and are
linked where they overlap (BD-88 relates BD-36).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018nwZgNGyowcU1L8F49Z4sr
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018nwZgNGyowcU1L8F49Z4sr
A URL written in a task description or note, an epic or release description or a
custom field value renders as a link labelled with the URL as typed, and opens
outside the app rather than navigating it away. The plain pane of a repo file
preview linkifies URLs too, while boardown's own tokens there stay literal.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The task dialog's header carries a copy button right of the id, putting
`<type>(<ID>): <title>` on the clipboard with the type spelled the way a
conventional commit spells it. The clipboard behaviour is shared with the
Settings CLI row rather than repeated.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The task dialog carries a Commits panel below Details, listing the local
commits whose subject holds the task's id as a case-insensitive token, and
`boardown task commits <id>` reads the same list for an agent. Reading is
local and read-only: nothing is fetched and nothing is written. A new
`gitIntegration` key in config.yaml, absent meaning on, hides the panel.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Commits panel's row is a flex line: the monospaced short hash, then the
subject beside it on the same baseline. A subject too long for the width wraps
inside its own column, so every wrapped line starts at the subject's left edge
instead of running back under the hash.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A Commits row reads the subject first and the commit's date and time after it,
DD.MM.YYYY HH:MM in the reader's own time zone, held in its own column at the
row's end so a wrapped subject line never runs under it. The short hash is no
longer shown there; core carries the author date as ISO 8601 beside it, and the
CLI's `task commits` keeps publishing { hash, subject } alone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@grinev
grinev merged commit 53f2265 into main Sep 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant