thatguygriffandClaude Opus 5
cf97f0dc2a
Refreshing rebuilt the whole tree, and TreeView.reload() with no argument drops the scroll position. Watching a job meant the view jumped every fifteen seconds. The provider now reconciles instead of replacing. update() rebuilds from the store, matches rows to the existing nodes by identifier, copies the rendered fields onto them, and reports the topmost rows that actually changed; main.js reloads just those. Node identity survives the merge, which is what makes a targeted reload possible. An open row that fetches its own children has that cache dropped so it refetches — the running-job path. A job finishing now reloads one run's row and nothing else. Sections also each describe what they draw, so a section only rebuilds when its own content moved: run activity no longer disturbs the pull request list, and an idle tree is left alone entirely. This does not slow anything down — a section showing a run in progress still updates on every poll, and contributes a time bucket so its elapsed clock keeps moving. A row set changing at the root still needs a whole-tree reload; there the selected row is re-revealed afterwards, which is the closest thing to a scroll anchor Nova exposes. Adds seventeen checks: no-op updates reporting nothing, a finishing job naming only its own row, node identity surviving, a new run reloading just its workflow group, and a new workflow escalating to a full reload. 168 checks total. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01MQuusXgZC2dzwpJJ1qhtti
35 lines
2.0 KiB
Markdown
35 lines
2.0 KiB
Markdown
## Version 1.0
|
|
|
|
Initial release.
|
|
|
|
- **Current Branch** sidebar section with the pull requests and workflow runs for
|
|
the checked-out branch, plus a configurable branch filter.
|
|
- **Workflows** section grouping every run by workflow file, expanding into jobs,
|
|
steps, and artifacts. Servers older than Gitea 1.24 fall back to a flat recent
|
|
runs list.
|
|
- **Pull Requests** section across every discovered repository, expanding into
|
|
reviews, review comments, and changed files.
|
|
- **Settings** section showing per-instance connection state and per-repository
|
|
Actions secrets and variables.
|
|
- Run control: re-run a run, re-run failed jobs, re-run a single job, cancel.
|
|
- Job logs opened in the editor, optionally saved under `.tmp/gitea-logs/`.
|
|
- Artifact download, reveal in Finder, and open.
|
|
- Pull request Markdown overview, unified diff, per-file diff, branch checkout,
|
|
creation, merge with all four Gitea strategies, and close.
|
|
- Reviews: approve, request changes, comment, reply, resolve, unresolve, and
|
|
adding a comment on the line under the cursor from the editor.
|
|
- Review comments for the current branch published as editor issues.
|
|
- Multiple Gitea instances, routed by git remote host, with tokens stored per
|
|
instance in the macOS Keychain.
|
|
- Support for instances that answer SSH on a different hostname than their web
|
|
UI. The mapping is detected from the `ssh_url` a repository advertises and
|
|
saved as a host alias, so later repositories on that host resolve without a
|
|
lookup; it can also be set by hand, and an unresolved host is reported in the
|
|
sidebar with an action to fix it.
|
|
- Adaptive polling and a notification when a workflow run fails.
|
|
- Gitea Actions CI running the test suites, script syntax checks, manifest
|
|
validation, and a generated-image check.
|
|
- The sidebar keeps its open rows and its scroll position while it refreshes.
|
|
Only the rows that actually changed are reloaded, so watching a running job
|
|
updates that job's row and leaves the rest of the tree where it is.
|