You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1030d44
Browse filesBrowse the repository at this point in the historyBrowse files
fix(web): gate the add-project intent on projectManagement
Upstream pingdotgg#26238 stopped checking `projectCloneTracking`, so adding a project
by URL now calls `startProjectClone`, which Moatless does not dispatch. The
palette action was already filtered, but `openCommandPalette({ open:
"add-project" })` and the pull request list's empty-state button still opened
the flow. The gaps entry now records that Moatless folds `context` itself
(soaplabs/moatless#1326).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
"mustSurvive": "Re-apply list filtering gates. FEATURES.projectManagement also hides the New project affordance wherever it is offered: both sidebars and the draft hero's project picker, which upstream grew a New project menu item on 2026-09-05. A Moatless deployment creates projects from its own admin surfaces, so an enabled New project entry here leads nowhere."
1520
+
"mustSurvive": "Re-apply list filtering gates. FEATURES.projectManagement also hides the New project affordance wherever it is offered: both sidebars and the draft hero's project picker, which upstream grew a New project menu item on 2026-09-05. A Moatless deployment creates projects from its own admin surfaces, so an enabled New project entry here leads nowhere. The same flag drops `openCommandPalette({ open: \"add-project\" })` in commandPaletteBus.ts, the backstop for every caller of that intent, and hides the pull request list's empty-state Add project button."
0 commit comments