$ git branch -a develop * master $ git tag -l 0.1.0 $ git flow release finish '0.1.0' Already on 'master' Deleted branch release/0.1.0 (was f9cdbf0).Īfter the “git flow release finish” command runs, the release branch should be deleted and a new Git tag exists in the repository. When the release is stable, run the “git flow release finish” command. $ git flow release start 0.1.0 Switched to a new branch 'release/0.1.0' $ git branch -a develop master * release/0.1.0 Use the “git flow release start” command to create the release branch. $ git flow feature finish feature_branch Switched to branch 'develop' $ git branch -a * develop master When the feature is finished, the feature branch is deleted. Notice this adds a new branch named “feature/feature_branch.” $ git flow feature start feature_branch Switched to a new branch 'feature/feature_branch' $ git branch -a develop $ git branch -a * develop master $ git tag -lĬreate a feature branch to represent some work that will make the project feature complete. Only two branches exist after initialization, and there are no tags. $ git flow init Initialized empty Git repository in C:/_tools/temp/.git/ To work with the release branch, first initialize a Gitflow repository. The following set of commands takes you through the Gitflow release branch process lifecycle. But the key difference is that release branches are created off the development branch, while hotfix branches are created directly off the master/main branch. Release and hotfix are the only two Gitflow branches that get merged directly into master. The Gitflow release branch is made from the develop branch and gets merged into both master and develop when finished.
0 kommentar(er)
