feat: Add noMerge config option with auto-detection for GitHub Actions

[BYK]

Summary

Add noMerge as a config option in .craft.yml that mirrors the --no-merge CLI flag. When enabled, the release branch is not merged back into main/master after publishing.

Key features:

• New noMerge: true/false option in .craft.yml
• Auto-detects compiled GitHub Actions (Node.js actions with dist/ folder) and defaults to noMerge: true
• Clear logging indicates why merging was skipped (CLI, config, or auto-detected)
• Warns if --merge-target is specified but ignored due to noMerge

Why?

Compiled GitHub Actions (built with @vercel/ncc or esbuild) need the dist/ folder in release branches but typically gitignore it on main. Merging the release branch back would overwrite the clean main with compiled artifacts.

Example

# .craft.yml
minVersion: '2.21.0'
noMerge: true  # Optional - auto-detected for compiled GitHub Actions
targets:
  - name: github

Changes

• src/schemas/project_config.ts - Added noMerge to config schema
• src/utils/detection.ts - New file with isCompiledGitHubAction() detection
• src/config.ts - Added getNoMergeConfig() accessor function
• src/commands/publish.ts - Modified merge logic to respect config
• Added tests for config parsing and detection

^{Cursor Bugbot reviewed your changes and found no issues for commit 8f2ab72}

[BYK]

@cursor review

[cursor]

Skipping Bugbot: Bugbot is disabled for this repository

[BYK]

@sentry review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}