-
Notifications
You must be signed in to change notification settings - Fork 527
Is this project still alive? #472
Comments
Indeed, I was wondering why the Any explanation/reason @petervanderdoes ? |
People are adopting trunk based development over gitflow since it's less bulky/procedural. |
Can you explain the term "trunk based development" please. Btw: nvie/gitflow#6484 |
Not true! I use GitFlow more than any other type of strategy. Yes, on some small, one developer or very small team projects, I use the GitHub strategy. For HIPPA, PCI, any really any other security intensive projects and when I'm the leader, Git Flow type of workflow only! Other times, prior to the project, the team and I sit down, and discuss a strategy. Sometimes we use Github Flow, OR Git Flow, OR GitLab Flow, BUT, more times than not, we create our own workflow/strategy that works best for our project and team. And again, more times than not, it's dynamic. As times goes on, we refine the flow that works best to our needs. But, at the end of the day, many of the features in this package are in use with almost all of our workflows that we use. It's said to see that it has not been updated in years. |
As of 2023 https://github.com/CJ-Systems/gitflow-cjs is active |
Last commit 3 years ago, over a hundred issues and 30 PRs
Is this project still maintained? Are there any evergreen forks in the wild? funnily enough I got here from reading the nvie/gitflow#6452 issue
I'd appreciate if there was at least a "not actively maintaned" notice on the README.
The text was updated successfully, but these errors were encountered: