gitflow VS release-please

Compare gitflow vs release-please and see what are their differences.


Git extensions to provide high-level repository operations for Vincent Driessen's branching model. (by nvie)


generate release PRs based on the spec (by googleapis)
Our great sponsors
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarLint - Clean code begins in your IDE with SonarLint
  • SaaSHub - Software Alternatives and Reviews
gitflow release-please
113 35
26,103 2,058
- 8.2%
0.0 9.6
3 months ago 2 days ago
Shell TypeScript
GNU General Public License v3.0 or later Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of gitflow. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-02.
  • What "new-to-you" tool did you recently start using that just changed your workflow for the better?
    12 projects | | 2 Jan 2023
    For us it was git-flow ( A straightforward yet effective way to impress momentum in the use of basic strategies: master branch is for production, feature/... for developing new stuff, devel(op) branch for preparing next release (merging feature and hotfixes), release/... for release candidates, hotfix/... for zero-day or fixes on production... Absolutely nothing new, absolutely easy to do.
  • Ask HN: What made you finally grok Git?
    3 projects | | 18 Nov 2022
    As a beginner - each of stash, branch, staged and remote is just a swimlane, kinda like illustration here: but can't remember where did I read it initially
  • Learning git as a beginner
    3 projects | | 6 Oct 2022
  • Does this look like a OK git flow for small team for manual deployment without CI/CD tools? (more in comments)
    2 projects | | 7 Sep 2022
    Another thing that other suggested me in the comments is to use trunk-based development, which from what I understand is to only create branches directly from master, for anything you do: bugfix, hotfix, feature. Keep them short-lived, then merge back to master. It also sounds like a good idea for me (I've been getting so many options in this short time and overwhelming). Do you think trunk based development is also a good idea? It soudns similar to what GitHub suggests (GitHub Flow:, and even the guy I first got the idea of the drawing above, suggested to use something like GitFlow:
    2 projects | | 7 Sep 2022
    Please, also consider that the GitFlow's owner himself nowadays discourages teams from using GitFlow, as he commented in his web page
  • How well do you need to know git?
    2 projects | | 28 Aug 2022
    if you can perform all steps described in this doc (which is similar to what most companies do), you are good:
  • Be effective with Bitrise CI for Android — the lessons I learned the hard way.
    2 projects | | 26 Aug 2022
    There is git flow approach in place, which usually means multiple feature *branches exist at the same time in a remote repository. There is at least one *pull request per story. Each pull request needs to go through an integration* process* meaning the newest commit in a pull request triggers a fresh CI build. That’s being done in order to ensure the newest change won’t introduce any flaws. Yep, automation and unit test suites test each software incrementation. Software Engineers in Test (SET) writes automation tests as “a part of“ the feature in some cases.
  • Managing Embedded SW revs?
    4 projects | | 10 Aug 2022
    This is more easier version of that:
    4 projects | | 10 Aug 2022
    Under Linux I use gitflow and gitversion. The former helps me with branch and tags management, the latter keep tracks of the semantic version in a semi-automatic fashion (given a branch/commit/tag it generate a semver automatically based on the repo log). Gitflow should be supported by GUI tools too, but I'm more a CLI guy.
  • Well-Architected Framework Review - Part III reliability
    5 projects | | 22 Jul 2022
    Manage change in automation: Changes to your infrastructure should be made using automation and IaC Tool, such as CDK or terraform. The changes that need to be managed include changes to the automation, which then can be tracked and reviewed, for example, in a VCS such as git and services such as GitHub with a branching model, such as git-flow.


Posts with mentions or reviews of release-please. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-14.

What are some alternatives?

When comparing gitflow and release-please you can also consider the following projects:

argocd-example-apps - Example Apps to Demonstrate Argo CD

semantic-pull-requests - :robot: Let the robots take care of the semantic versioning

cz-cli - The commitizen command line utility. #BlackLivesMatter

commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:


conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.

git-hook-conventional-commits-validator - A Git pre-commit hook which validates commit messages using Conventional Commits standard

laragon - Laragon is a portable, isolated, fast & powerful universal development environment for PHP, Node.js, Python, Java, Go, Ruby. It is fast, lightweight, easy-to-use and easy-to-extend.

semver - Semantic Versioning Specification

vite - Next generation frontend tooling. It's fast!

terraform-provider-wireguard - Terraform provider for WireGuard metadata