bug: init should not exit silently when config exists (no overwrite)

[tanmayjoddar]

Problem

If apidrift.config.json already exists and the user answers No to overwrite, apidrift init returns immediately and provides no guidance.

Where

• src/commands/init.js

Acceptance Criteria

• If config exists and overwrite is declined, command still prints helpful next steps (at minimum: how to set tokens via .env/env vars)
• Must not modify the existing config when overwrite is declined
• Exit code remains 0

Nice-to-have (still beginner-friendly)

• Offer to create a .env file with placeholder tokens and/or ensure .env is in .gitignore

[vivekyadav-3]

Hi! I have submitted a pull request that fixes this issue. The code has no conflicts and is clean. Please review and merge when you get a chance! Thanks!

[basantnema31]

Hi @tanmayjoddar! I'd love to fix this UX bug under GSSoC '26.

My proposed implementation:
Inside the init command logic, when fs.existsSync(configFile) returns true, instead of just silently returning, I will output a clear terminal error message (e.g. Error: Configuration file already exists. Use --force to overwrite.) and ensure the process exits with a non-zero code (like process.exit(1)) so CI pipelines can correctly detect the failure.

Could you assign this to me?

[saurabhhhcodes]

Hi, I'd like to work on this under GSSoC 2026. My plan is to reproduce the silent no-overwrite path in init, add a focused regression test around the existing-config flow, and make the CLI return a clear non-destructive message instead of failing quietly. Please assign this to saurabhhhcodes if it fits your current queue.