Note
Reviews paused
It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.
- Last reviewed commit: b5f498c5bbdef45c1f3b0ebde01cee776078f2e1
Use the following commands to manage reviews:
@coderabbitai resumeto resume automatic reviews.@coderabbitai reviewto trigger a single review.
Use the checkboxes below for quick actions:
- Resume reviews
- Trigger review
Walkthrough
-
The change adds a custom-title flag to project records and shells, backfills it with migration 82, and uses it when updating group titles and deriving repository group labels.
Changes: Custom project titles
Layer / File(s) Summary Persist the custom-title flag
packages/contracts/src/orchestrationProject.ts,apps/server/src/persistence/Migrations/...,apps/server/src/persistence/Migrations.ts,apps/server/src/orchestration-v2/ProjectStore.ts,apps/server/src/orchestration-v2/*.test.ts,apps/server/src/persistence/reconcileV2PreviewMigration.test.tsThe project shell and database projection now carry hasCustomTitle. Migration 82 adds and backfills the database field. Project updates set the flag, and upserts preserve an existing custom title against incoming non-custom titles. Tests cover persistence, migration, and updated project fixtures.Apply explicit group-title edits
apps/web/src/components/settings/ProjectSettingsPanel.logic.ts,apps/web/src/components/settings/ProjectSettingsPanel.tsx,apps/web/src/components/settings/ProjectSettingsPanel.logic.test.tsThe group-title update check now considers each member’s title and custom-title flag. An edited title triggers an update when a member is not yet marked custom, even if the title matches the folder default. Derive labels from custom titles
packages/client-runtime/src/state/projectGrouping.ts,packages/client-runtime/src/state/projectGrouping.test.tsGroup-label derivation now uses custom-title flags to distinguish an explicit repository-name title from a default title. Estimated code review effort: 3 (Moderate) | ~20 minutes
Change: Bug fix · Severity of issue fixed: Low
Possibly related issues
- Issue 26296 reports that a grouped project label can replace an explicit repository-name title. This change uses the custom-title flag when deriving group labels.
Suggested labels:
bugfixSuggested reviewers:
juliusmarminge,t3dotgg
Merge Risk: External image Moderate · up to b5f49
-
Databases created by the earlier build of this PR may fail to start after upgrade because migration 81 was renumbered. Add a reconciliation path before merging, or confirm that no such databases exist.
Pre-merge checks: Passed 4
-
Check name Status Explanation Title check Passed The title clearly identifies the primary fix: preserving grouped project renames to repository names. It is concise and uses the repository's conventional commit format. Description check Passed The description includes all required sections: Problem, Change, Scope and approval context, and Verification. It explains the behavior, implementation, linked issue, test results, browser verificatio… Linked Issues check Passed Issue #15049requires grouped projects to save a rename that removes the owner or group prefix while retaining the repository name. The PR records explicit title updates inProjectStore, exposes `ha…Out of Scope Changes check Passed The changes stay within issue #15049. The migration, store updates, shell contract, grouping logic, settings logic, fixtures, and regression tests support title persistence and display for grouped pro…Full details: Description check
-
Explanation
The description includes all required sections: Problem, Change, Scope and approval context, and Verification. It explains the behavior, implementation, linked issue, test results, browser verification, limitations, and migration follow-ups. It is detailed and directly related to the changes.
Full details: Linked Issues check
-
Explanation
Issue
#15049requires grouped projects to save a rename that removes the owner or group prefix while retaining the repository name. The PR records explicit title updates inProjectStore, exposeshasCustomTitlethroughOrchestrationProjectShell, uses the flag inderiveProjectGroupLabelandprojectGroupTitleNeedsUpdate, and adds regression tests for matching repository names, migration backfill, and later updates.
Full details: Out of Scope Changes check
-
Explanation
The changes stay within issue
#15049. The migration, store updates, shell contract, grouping logic, settings logic, fixtures, and regression tests support title persistence and display for grouped projects. No unrelated change is demonstrated by the supplied whole-PR summary.
-
Finishing Touches
-
Generate docstrings
-
- Commit to this branch
- Create a new PR
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts