Add Single-Branch Git Clone to n8n: Improve Workflow Speed and Efficiency

Executive teams adopting n8n for developer environment provisioning should treat this community request as low-effort, high-impact. Cloning entire repos with many branches is unnecessary for most automation flows and increases latency, network cost, and ephemeral storage usage. Allowing `git clone -b --single-branch` or a tag will shave minutes off workflows and reduce failure surface when network conditions are marginal.

From an engineering perspective, exposing branch/tag selection is a straightforward extension: add optional parameters in the Git node UI and map them to `git clone` arguments. Validate input to avoid injection and provide sensible defaults. For organizations, the change improves developer productivity, reduces resource consumption on CI agents and ephemeral containers, and simplifies compliance by limiting the code surface pulled into automation environments.

Operational leaders should consider this as part of a broader optimization checklist: prefer shallow clones (`--depth=1`) alongside single-branch clones, cache dependencies, and profile common workflows to quantify savings. Product teams at n8n can prioritize contributions by surfacing usage telemetry (how many users clone large repos) and offering this change as a small, well-scoped feature request, possibly community-contributed.

Actionable next steps: (1) Productize the option with clear UX (branch vs tag input, checkbox for single-branch), (2) document security implications and recommended flags like `--depth=1`, and (3) run a short A/B test with high-branch repos to measure time and bandwidth improvements. These moves deliver measurable value with minimal development risk.