[furedea-agent]

概要

gh-dash の初期区分（author:@me など）は，Issue と PR をほぼすべて app/furedea-agent が作る運用では常に空になる．区分を自前で定義し，起動したリポジトリの開いている Issue と PR がすべて見えるようにする．

• Issues: Open（is:open -author:app/renovate）
• PRs: Open（is:open）
• 各ビューに All repos（is:open user:furedea，Issues は -author:app/renovate 付き）を追加．リポジトリ外で起動して smart filtering が効かない場合に，自分のリポジトリ横断の一覧になる．リポジトリ内では smart filtering により repo: が付き Open と同じ内容になるが，許容する
• Open 区分には repo: は書かず，smartFilteringAtLaunch で起動したリポジトリに絞る
• defaults.view，refetchIntervalMinutes，smartFilteringAtLaunch は維持

検証

• nix flake check 通過
• kaito@mbp の home 構成をビルドし，生成された config.yml に両区分が出力されることを確認

Closes #446

🤖 Generated with Claude Code

[furedea]

@codex review

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-10T17:00:50.376641Z We couldn’t complete this review. Comment @codex review to try again.	73d94bb	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[github-actions]

[P2] These sections rely only on smartFilteringAtLaunch to add repo:. gh-dash adds that only when it starts inside a git repo that has a GitHub remote. Started anywhere else (for example ~), is:open and is:open -author:app/renovate run as GitHub-wide searches and show unrelated public issues and PRs. The old defaults were scoped to @me, so that case used to give useful results. To keep it useful, add a second section scoped to you, like is:open user:furedea (or org:/involves:). Another option is to note that gh-dash should only be launched from inside a repo.

[furedea-agent]

Fixed in the latest commit: each view now has a second section, All repos (is:open user:furedea, plus -author:app/renovate for issues). The first Open sections stay unscoped so smart filtering narrows them inside a repo. Outside a repo, All repos gives a cross-repo list limited to the user's repositories.

[github-actions]

Review summary

This is a small config-only change that adds custom gh-dash issuesSections and prsSections. The Nix structure matches the home-manager programs.gh-dash.settings schema, and I found no correctness or security problems.

• [P2] The new filters have no repo:/user: scope. When gh-dash starts outside a GitHub repo, smart filtering is off and the sections become GitHub-wide searches (details in the inline comment).

There are no blocking findings. This repo has no tests for this config. The PR's nix flake check and the check of the generated config.yml are enough for it.

🤖 Generated with Claude Code

[furedea]

@codex review

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[github-actions]

P2: With smartFilteringAtLaunch = true, gh-dash scopes every section that has no repo: in its filter to the current repo at launch. That includes this "All repos" section (and the matching one under prsSections). Started inside a repo, "All repos" will probably show the same results as "Open" until you press t on that section. GitHub's handling of user: combined with an added repo: is also unclear. The PR description lists only the Open sections, so these extra sections look unplanned. Either remove them, or check that they actually show cross-repo results when gh-dash starts inside a repo.

[github-actions]

Review summary: the change is small and the Open sections match the PR description. One finding:

• P2: The All repos sections in issuesSections and prsSections are not in the PR description. Because smartFilteringAtLaunch applies to every section without a repo: filter, these sections are probably scoped to the current repo at launch, which would make them duplicates of Open until toggled with t. Please confirm they behave as intended or remove them.

No blocking issues. This is declarative config, so the flake check and build verification described in the PR are reasonable; no extra tests needed.

[furedea-agent]

All repos is intentional: it addresses the earlier P2 (unscoped sections become GitHub-wide searches outside a repo). Inside a repo, smart filtering adds repo: so it matches Open; that duplication is accepted. The PR description now documents these sections.