sb-ship

To graduate experimental React components from Storybook to production without losing design history, use a copy-based promotion workflow instead of destructive file moves. This preserves the original experiment files as a historical reference.

The best way to promote approved Storybook experiments to a production React codebase is to copy the component files to the production directory, update metadata tags to mark the experiment as chosen, and optionally use ast-grep to refactor import paths across the codebase.

Yes, you need git and bash installed to graduate Storybook components to production. These dependencies are required to execute the copy operations, manage repository state, and perform the preservation-first graduation workflow for your React components.

Ast-grep optionally refactors import paths for React components by searching and rewriting code syntax trees across the codebase. This ensures that when a Storybook experiment graduates to production, all internal project references are automatically updated to the new file location.

You should avoid using a copy operation to promote Storybook experiments if your goal is to completely remove the original experimental files from your exploration track. The preservation-first approach intentionally keeps the design history intact for future audit trails.