Where to Branch for n8n Contributions: Practical Guidance for Contributors and Teams
Confusion about which branch to use-master being outdated and multiple release branches present-reflects common challenges in open-source project workflows. Contributors should consult repository documentation for the canonical base, use feature branches from the active development branch, and follow CI and testing guidelines to ensure smooth merges.
When a repository's default branches are unclear (for example master being legacy while release/2.x branches are active), the first step is to consult the repo's README and CONTRIBUTING.md; maintainers usually document the recommended base branch. If that guidance is absent, inspect recent merge activity and CI pipelines to identify the active integration branch (often named main, develop, or a versioned branch like release/2.x).
Recommended contribution workflow: fork the repository, sync your fork with the identified active branch, and create a descriptive feature branch (eg, feat/bugfix-short-description). Keep changes focused and small, rebase frequently against the upstream active branch to avoid drift, and include tests and linting changes to satisfy automated checks. If the project uses a release branch model, target your PR to the branch that matches the release cadence you intend to affect.
For teams and businesses contributing upstream, establish internal policies: designate one or two maintainers to shepherd PRs, run the full test suite and end-to-end checks locally (using Docker or the repo's specified environment), and document environment setup to reduce onboarding friction. If older branches like master are still present but deprecated, add a clear notice and protect the canonical branch to prevent accidental merges.
Finally, communicate with maintainers when in doubt. Open an issue detailing your intended change and ask which branch to target; many projects will respond quickly and may create a temporary branch if needed. This reduces wasted effort and ensures your contribution aligns with release plans.
Original Source
n8n Community