detect-release-scope

To determine release scope from git changes, analyze modified, staged, untracked, and deleted file paths. This classifies changes into marketplace, plugin-specific, or variant scopes, applying dominance rules to pick a single scope or report ambiguity with counts.

Automating marketplace versus plugin release targeting requires inspecting git changes and applying dominance rules to classify the primary scope. This produces structured output with per-scope evidence and warnings to guide publishing decisions without manual path inspection.

Yes, you can use git workflow analysis to detect variants release scope. By examining modified, staged, and untracked file paths, the analysis classifies whether changes fall under variants, marketplace, or plugin-specific contexts for accurate versioning.

No, you do not need external dependencies to analyze git changes for release scope. The process operates using standard git tooling, evaluating modified and untracked files to output the classified scope, current branch, and relevant warnings.

Scope classification handles ambiguous git changes by applying dominance rules to select a primary scope when possible. When multiple directories are affected, it reports ambiguity with counts and provides warnings to guide your publishing decisions.