Repository navigation
Replies: 3 comments
|
+1, project exclusion alone would solve it for me I keep t3code itself as a project only to read the source when I check bugs or features. Its PRs flood the mobile PR list and I can't find the ones from my own projects. The project filter picks one project, and I want all of them except t3code |
Per-project feed rules would fit my workflow well, because what I want to see depends strongly on my role in each repository, and that preference tends to stay stable over time. As a maintainer, I may want visibility into every open PR in a repository. As an occasional contributor, I usually want to follow my own PRs and those waiting on my review or action. Simply adding a repository to Projects should not mean taking on its entire PR queue. The multi-select and exclusion proposals in #11134 and #33520 would help with choosing which repositories to include. But even with those controls, it would still be difficult to express a combined feed like:
A global project selection plus a global involvement filter cannot express those different rules together. I would need to keep switching between separate views. This feels consistent with the idea of the PR page as a workspace inbox: each repository contributes the work I have chosen to follow, based on my role there. I could set those rules once and return to one useful combined feed. For a first version, persistent per-project choices such as All PRs / Waiting on me / Authored by me / Exclude would cover my main need. Individual PR hiding could come separately. |
|
I built the "Project C: exclude from the feed" part of this, using the control the Issues page already has. Since #38799, Issues lets you uncheck projects under Filters → Projects. This branch gives the Pull requests page the same checklist: Branch: https://github.com/naxhh/t3code/tree/feat/pr-list-hide-projects (diff against main)
Related: #11134 and #33520 ask for the broader is/is-not filters; this covers only the project part. I'm not on the vouched list, so I'm leaving it here rather than opening a PR. Happy to open one if a maintainer wants it. I'm not vouched so leaving the branch here |

Uh oh!
There was an error while loading. Please reload this page.
What happened
The PR feed includes projects and individual PRs I do not want to see. I want persistent settings that combine different rules:
These rules should work together in one combined feed and persist between visits.
Diagnosis
The v0.1.5 source stores one PR view preference with a project selection and involvement filter. It does not provide per-project feed rules or individual PR exclusions.
Relevant source:
pullRequestListPreferences.tsat v0.1.5 andusePullRequestListView.tsat v0.1.5.This is a feature request. Project exclusion has been proposed before; the related work below does not cover the full combination requested here.
Steps to reproduce
Actual: The available filters cannot save this combined feed.
Expected: Persistent per-project rules support authored-only, all PRs, and exclusion, with the ability to hide individual PRs.
Version
0.1.5, confirmed by the user and local client/server version information.
Environment
T3 Code Desktop on macOS arm64, connected to the local server on the same Mac.
Evidence
The user supplied a screenshot of the populated PR feed and its “Others” section. Source inspection found a single saved preference object. Live UI reproduction was not performed.
The screenshot is omitted because it includes company repository and author information.
Related issues and pull requests
No exact match for individual PR hiding or mixed per-project involvement rules was found in the searches performed.
Fix applied or workaround
No changes applied. Switching project and involvement filters manually provides separate subsets, but does not provide the requested combined feed.
Filed by
Codex, gpt-6.1-sol, through T3 Code triage.
All reactions