Skip to content

Commit e4fb6d7

Browse files
authored
Update Git flow section in documentation
Removed image reference and clarified Git flow description.
1 parent 5a1d357 commit e4fb6d7

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

learn-pr/github/introduction-to-github/includes/3-components-of-github-flow.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,8 +84,6 @@ Now that we know the basics of GitHub we can walk through the GitHub flow and it
8484
8585
## Git flow
8686
87-
:::image type="content" source="../media/2-git-flow-image.png" alt-text="Diagram illustrating the Git flow workflow with parallel lanes for feature branches, develop, release branches, hotfixes, and master. It shows how features are merged into develop, release branches are created from develop, hotfixes are branched from master, and all changes are eventually merged back into master and develop with tagged versions." border="false":::
88-
8987
While GitHub Flow is a lightweight workflow designed for continuous delivery, **Git flow** is a more structured branching model often used in release-driven environments. Git flow has been around longer than GitHub Flow, and you may still see the term **`master`** used instead of **`main`** as the default branch.
9088
9189
### Git flow Branch Types

0 commit comments

Comments
 (0)