SaaSHub helps you find the best software and product alternatives Learn more →
Gitflow Alternatives
Similar projects and alternatives to gitflow
-
-
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
release-please
generate release PRs based on the conventionalcommits.org spec
-
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.
-
terraform-provider-wireguard
Terraform provider for WireGuard metadata
-
-
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
-
-
git-gui
Tcl/Tk based UI for Git. I am currently acting as the project's maintainer.
-
-
-
TypeScript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
-
-
-
Previous Serverless Version 0.5.x
⚡ Serverless Framework – Build web, mobile and IoT applications with serverless architectures using AWS Lambda, Azure Functions, Google CloudFunctions & more! –
-
styled-components
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
react-hook-form
📋 React Hooks for form state management and validation (Web + React Native)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
gitflow reviews and mentions
-
What "new-to-you" tool did you recently start using that just changed your workflow for the better?
For us it was git-flow (https://github.com/nvie/gitflow). 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?
As a beginner - each of stash, branch, staged and remote is just a swimlane, kinda like illustration here: https://nvie.com/posts/a-successful-git-branching-model/ but can't remember where did I read it initially
- Learning git as a beginner
-
Does this look like a OK git flow for small team for manual deployment without CI/CD tools? (more in comments)
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: https://docs.github.com/en/get-started/quickstart/github-flow), and even the guy I first got the idea of the drawing above, suggested to use something like GitFlow: https://nvie.com/posts/a-successful-git-branching-model/
Please, also consider that the GitFlow's owner himself nowadays discourages teams from using GitFlow, as he commented in his web page https://nvie.com/posts/a-successful-git-branching-model/
-
How well do you need to know git?
if you can perform all steps described in this doc (which is similar to what most companies do), you are good: https://nvie.com/posts/a-successful-git-branching-model/
-
Be effective with Bitrise CI for Android — the lessons I learned the hard way.
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?
This is more easier version of that: https://nvie.com/posts/a-successful-git-branching-model/
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
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.
-
A note from our sponsor - #<SponsorshipServiceOld:0x00007fea5944d590>
www.saashub.com | 1 Feb 2023
Stats
nvie/gitflow is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.