Merge pull request #1226 from objectstack-ai/copilot/restrict-storybook-tests-on-push

CI: Run Storybook tests only on `main` pushes

Author: hotlong

.github/workflows/storybook-tests.yml

@@ -1,20 +1,14 @@
 name: Storybook Tests
 on:
   push:
-    branches: [main, develop]
+    branches: [main]
     paths:
-      - 'packages/**'
-      - '.storybook/**'
-      - 'pnpm-lock.yaml'
-  pull_request:
-    branches: [main, develop]
-    paths:
-      - 'packages/**'
-      - '.storybook/**'
-      - 'pnpm-lock.yaml'
+      - "packages/**"
+      - ".storybook/**"
+      - "pnpm-lock.yaml"
 
 concurrency:
-  group: storybook-tests-${{ github.event.pull_request.number || github.ref }}
+  group: storybook-tests-${{ github.ref }}
   cancel-in-progress: true
 
 permissions:
@@ -39,8 +33,8 @@ jobs:
 
       - uses: actions/setup-node@v6
         with:
-          node-version: '20'
-          cache: 'pnpm'
+          node-version: "20"
+          cache: "pnpm"
 
       - name: Turbo Cache
         uses: actions/cache@v5
@@ -80,10 +74,3 @@ jobs:
 
       - name: Run Storybook tests
         run: pnpm storybook:ci
-
-      - name: Run visual regression tests
-        if: github.event_name == 'pull_request'
-        run: |
-          concurrently -k -s first \
-            "pnpm storybook --no-open" \
-            "wait-on tcp:6006 && pnpm storybook:test:snapshot"

CHANGELOG.md

@@ -23,6 +23,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- **Storybook CI scope reduced** (`ci`): Updated `.github/workflows/storybook-tests.yml` to run only on `push` to `main` (removed `pull_request` and `develop` triggers) and removed the PR-only visual regression step to reduce heavy CI load on contributor PRs.
+
 - **Merged ObjectManagerPage into MetadataManagerPage pipeline** (`@object-ui/console`): Removed the standalone `ObjectManagerPage` component. Object management is now fully handled by the generic `MetadataManagerPage` (list view) and `MetadataDetailPage` (detail view) pipeline. The object type config in `metadataTypeRegistry` uses `listComponent: ObjectManagerListAdapter` for the custom list UI and `pageSchemaFactory: buildObjectDetailPageSchema` for the detail page, eliminating redundant page code and centralizing all metadata management through a single architecture.
 
 - **`listComponent` extension point on MetadataTypeConfig** (`@object-ui/console`): New optional `listComponent` field allows metadata types to inject a fully custom list component into `MetadataManagerPage`, replacing the default card/grid rendering. The page shell (header, back button, title) is still rendered by the generic manager. `MetadataListComponentProps` interface provides `config`, `basePath`, `metadataType`, and `isAdmin` to the custom component.