Create a new pipeline
If you already have an existing pipeline, go to your pipeline selection in the top left corner and choose Create new pipeline:
If you do not have any pipelines, choose Create a pipeline on the landing page:
Navigate the setup wizard
You’ll first see the default expanded branching model. To switch:
Select Change under Branching strategy:
Choose Gitflow and continue:
You can connect Jira, Azure DevOps or Salesforce for issue/ticket tracking, provided that connections are already configured. This can also be done later:
You can require pull request descriptions and choose whether reviewer settings should be copied between environments:
Select your VCS provider. Gitflow supports the same providers as existing Pipelines except for AWS CodeCommit:
Choose or create your repository. If you’re using Gitflow for the first time (meaning you not have an existing Gitflow repository), we recommend starting with a new repository so that your two long-lived branches begin in sync:
If you already have an existing Gitflow repository, we strongly recommend that your
mainanddevelopbranches are in sync before proceeding.
You will then select:
Your production branch (typically
mainormaster).Your integration (
develop) branch, the source for new features and the integration point for ongoing work. We recommend letting Gearset create a newdevelopbranch frommainif this branch does not already exist:
If you are creating a new
developbranch, you can name it accordingly:
Populate your repository. You can either:
Allow Gearset to auto-detect metadata to include, or
Choose a saved metadata filter.
Once your metadata is selected, you can create your Gitflow pipeline:
You have now created a Gitflow pipeline. The next step is to add your environments.