fix(cli): support --yes flag for unattended dataset import

When using `sanity dataset import` with a non-existing target dataset,
the command previously always prompted for confirmation to create it,
even when the --yes flag was provided.

This change:
- Adds -y/--yes flags to the import command's flag interface
- Auto-confirms dataset creation when --yes is provided
- Throws an error if --yes is used without specifying a target dataset
- Documents the flag in the help text

Fixes SAPP-3387

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: annez

packages/@sanity/cli/test/exportImport.test.ts

@@ -80,5 +80,19 @@ describeCliTest('CLI: `sanity dataset export` / `import`', () => {
       expect(result.stdout).toMatch(/done!/i)
       expect(result.code).toBe(0)
     })
+
+    testConcurrent('import with --yes creates non-existing dataset', async () => {
+      const newDataset = `${testRunArgs.dataset}-import-yes`
+      const result = await runSanityCmdCommand(studioName, [
+        'dataset',
+        'import',
+        testRunArgs.importTarballPath,
+        newDataset,
+        '--missing',
+        '--yes',
+      ])
+      expect(result.stdout).toMatch(/done!/i)
+      expect(result.code).toBe(0)
+    })
   })
 })

packages/sanity/src/_internal/cli/commands/dataset/importDatasetCommand.ts

@@ -22,6 +22,7 @@ Options
   --allow-failing-assets Skip assets that cannot be fetched/uploaded
   --replace-assets Skip reuse of existing assets
   --skip-cross-dataset-references Skips references to other datasets
+  -y, --yes Unattended mode, auto-confirm dataset creation prompts
 
 Rarely used options (should generally not be used)
   --allow-assets-in-different-dataset Allow asset documents to reference different project/dataset
@@ -53,6 +54,8 @@ interface ImportFlags {
   'allow-system-documents'?: boolean
   'replace'?: boolean
   'missing'?: boolean
+  'yes'?: boolean
+  'y'?: boolean
 }
 
 interface ParsedImportFlags {
@@ -136,7 +139,8 @@ const importDatasetCommand: CliCommandDefinition = {
       )
     }
 
-    const targetDataset = await determineTargetDataset(target, context)
+    const unattended = Boolean(args.extOptions.yes || args.extOptions.y)
+    const targetDataset = await determineTargetDataset(target, context, unattended)
     debug(`Target dataset has been set to "${targetDataset}"`)
 
     const isUrl = /^https?:\/\//i.test(file)
@@ -304,7 +308,11 @@ const importDatasetCommand: CliCommandDefinition = {
   },
 }
 
-async function determineTargetDataset(target: string, context: CliCommandContext) {
+async function determineTargetDataset(
+  target: string,
+  context: CliCommandContext,
+  unattended: boolean,
+) {
   const {apiClient, output, prompt} = context
   const client = apiClient()
 
@@ -322,17 +330,23 @@ async function determineTargetDataset(target: string, context: CliCommandContext
 
   let targetDataset = target ? `${target}` : null
   if (!targetDataset) {
+    if (unattended) {
+      throw new Error('Target dataset must be specified when using --yes flag')
+    }
     targetDataset = await chooseDatasetPrompt(context, {
       message: 'Select target dataset',
       allowCreation: true,
     })
   } else if (!datasets.find((dataset) => dataset.name === targetDataset)) {
     debug('Target dataset does not exist, prompting for creation')
-    const shouldCreate = await prompt.single({
-      type: 'confirm',
-      message: `Dataset "${targetDataset}" does not exist, would you like to create it?`,
-      default: true,
-    })
+    let shouldCreate = unattended
+    if (!unattended) {
+      shouldCreate = await prompt.single({
+        type: 'confirm',
+        message: `Dataset "${targetDataset}" does not exist, would you like to create it?`,
+        default: true,
+      })
+    }
 
     if (!shouldCreate) {
       throw new Error(`Dataset "${targetDataset}" does not exist`)