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:
Select the Gitflow branching strategy
You’ll first see the default expanded branching model. To switch:
Select Change under Branching strategy:
2. Choose Gitflow and continue through the setup wizard:
Integrate issue tracking (optional)
You can connect Jira or Azure DevOps, provided connections are already configured:
Configure pull request requirements
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 adopting Gitflow for the first time, we recommend starting with a new repository so that your long-lived branches begin in sync.
Enter a repository name and Gearset will create it in your VCS:
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 new integration/develop branch from main:
You can give this branch a name:
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:
Once the repository is populated with the metadata, the head of both the production and integration branches should be the commit from Gearset.
The next steps are to add environments to the pipelines. You can read more about that in the next article.