There are plenty of models how to do your branching in git. All of them are viable approaches with their respective pros and cons. So let's have a look at those branching strategies and where they are great and where they are falling off.
So let's deep dive into: Git-Flow, GitHub-Flow, Gitlab-Flow, Trunk Based Development.

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

There are many ways to organize your branches with git. In this article I want to show you 4 ways of doing so. We will see what are the pros and cons and when they are most applicable. So let's start. Git-Flow tries to be an universal branching strategy which covers a lot of scenarios. The main idea is you have a set of branches which have a specific responsibility.

Git-Flow, GitHub-Flow, Gitlab-Flow and Trunk Based Development explained

I love the simplicity in organizing the different methods with pro/con lists. Great job with this.

Apparently Gitflow is a legacy strategy according to this Atlassian tutorial. It looks like trunk-based workflows are a more future proof solution.
<a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow" target="_blank" rel="noopener nofollow">https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow</a>