Add repository organization and filtering controls - #32
Conversation
- Add persistent repository groups, aliases, pinning, and hidden state - Add search, project sections, context-menu actions, and organization dialog - Cover persistence, validation, storage errors, hidden repositories, and reordering
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 230a426ec7
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export function repositoryPreference( | ||
| organization: RepositoryOrganization, | ||
| path: string, | ||
| ): RepositoryPreference { | ||
| return organization.repositories[getRepoPathKey(path)] ?? emptyRepositoryPreference; |
There was a problem hiding this comment.
When the existing “Choose New Location” recovery flow replaces a recent repository with a new anchor path, preferences remain stored and looked up only under the old path key here. As a result, a successfully recovered repository silently loses its alias, project assignment, pinned state, and hidden state while leaving an orphaned entry behind; migrate the preference to the returned replacement anchor as part of recovery.
AGENTS.md reference: AGENTS.md:L3-L5
Useful? React with 👍 / 👎.
1 participant
Summary
Testing