開発が止まったgit-flowを作り直したgit-flow-nextが良さげかも
開発が止まったgit-flowとgitflow-avhを元にGoで作り直されたgit-flow-nextの紹介です。
kawarimidoll.com
November 8, 2026 at 12:10 AM
We adopted Gitflow a decade and a half ago and haven’t really had any issues since. I think Atlassian still has a decent article on it.
October 25, 2026 at 5:08 PM
We adopted Gitflow a decade and a half ago and haven’t really had any issues since. I think Atlassian still has a decent article on it.
No soy yo experto el Gitflow, pero que develop esté vacío y haya dos ramas hotfix está un poco mal, ¿no? XD
October 20, 2026 at 8:48 AM
No soy yo experto el Gitflow, pero que develop esté vacío y haya dos ramas hotfix está un poco mal, ¿no? XD
Se precisar de ajuda no Gitflow, tamo aí
October 19, 2026 at 8:40 PM
Se precisar de ajuda no Gitflow, tamo aí
Exatamente, eu ainda uso por costume, mas não tem necessidade nenhuma de usar gitflow trampando sozinho
anyway, vai dar certo <3
anyway, vai dar certo <3
October 19, 2026 at 8:57 PM
Exatamente, eu ainda uso por costume, mas não tem necessidade nenhuma de usar gitflow trampando sozinho
anyway, vai dar certo <3
anyway, vai dar certo <3
idk about pop tarts but can you explain gitflow without git?
September 24, 2026 at 8:52 PM
idk about pop tarts but can you explain gitflow without git?
PRs are too slow
Have an agent work as a release manager and merge branches, review just like old gitflow. Each agent can have its own commit identity with just vanilla git. Worktrees and branches should be enough to stop conflicts. All commits are local and push one PR once an evening
imo anyway
Have an agent work as a release manager and merge branches, review just like old gitflow. Each agent can have its own commit identity with just vanilla git. Worktrees and branches should be enough to stop conflicts. All commits are local and push one PR once an evening
imo anyway
September 24, 2026 at 6:04 PM
PRs are too slow
Have an agent work as a release manager and merge branches, review just like old gitflow. Each agent can have its own commit identity with just vanilla git. Worktrees and branches should be enough to stop conflicts. All commits are local and push one PR once an evening
imo anyway
Have an agent work as a release manager and merge branches, review just like old gitflow. Each agent can have its own commit identity with just vanilla git. Worktrees and branches should be enough to stop conflicts. All commits are local and push one PR once an evening
imo anyway
Yeah I have no idea what you're developing. If you care about that - great
If you are targeting a spec and having a swarm playwright or something maybe you'd prefer to "code" like you're making poptarts.
There's nothing you can do in git that you can't do in gitflow or dag
If you are targeting a spec and having a swarm playwright or something maybe you'd prefer to "code" like you're making poptarts.
There's nothing you can do in git that you can't do in gitflow or dag
September 24, 2026 at 8:48 PM
Yeah I have no idea what you're developing. If you care about that - great
If you are targeting a spec and having a swarm playwright or something maybe you'd prefer to "code" like you're making poptarts.
There's nothing you can do in git that you can't do in gitflow or dag
If you are targeting a spec and having a swarm playwright or something maybe you'd prefer to "code" like you're making poptarts.
There's nothing you can do in git that you can't do in gitflow or dag
リリース・本番障害対応の迷子をゼロに。GitFlowの全手順を完全網羅！王道のブランチ戦略をマスターしチーム開発の生産性を向上させよう。
・リリース: developからmainへPR
・ホットフィックス: main直系で迅速に修正
・同期: 必ずdevelopへ変更を還元
#GitFlow #開発手法
・リリース: developからmainへPR
・ホットフィックス: main直系で迅速に修正
・同期: 必ずdevelopへ変更を還元
#GitFlow #開発手法
Git Branch Development Workflow and best practices
### Release Workflow
1. When we are ready for release then we create branch likerelease/1.0.0 from develop branch
2. Do the release activities.
3. Raise a pull request to main/master and merge
4. Tag release on main/master
5. Sync develop branch with main/master to start with next release
medium.com
September 23, 2026 at 12:26 PM
GitFlow starts fights in team chats because everyone means something different by it.
Chad Michel breaks down the two-branch version we run on our own projects: develop for QA, staging, and preview, and main for production only.
Chad Michel breaks down the two-branch version we run on our own projects: develop for QA, staging, and preview, and main for production only.
Two Branches and Boring Deploys: A Simpler Take on GitFlow | Don't Panic Labs
Chad Michel walks through a two-branch GitFlow variant, develop and main, that keeps deploys predictable for small and medium teams.
dontpaniclabs.com
September 9, 2026 at 12:26 PM
GitFlow starts fights in team chats because everyone means something different by it.
Chad Michel breaks down the two-branch version we run on our own projects: develop for QA, staging, and preview, and main for production only.
Chad Michel breaks down the two-branch version we run on our own projects: develop for QA, staging, and preview, and main for production only.
git-flow-next 2.0 introduces shared, committable configuration via a .gitflow file, tab completion for both command forms, and a stricter, safer foundation across the board.
Check out what's new 👉 git-flow.sh/blog/posts/...
Check out what's new 👉 git-flow.sh/blog/posts/...
August 31, 2026 at 1:15 PM
git-flow-next 2.0 introduces shared, committable configuration via a .gitflow file, tab completion for both command forms, and a stricter, safer foundation across the board.
Check out what's new 👉 git-flow.sh/blog/posts/...
Check out what's new 👉 git-flow.sh/blog/posts/...
Trunk-based development won the branching war by default. Long-lived feature branches kept aging into merge horror stories, while small daily merges, short-lived branches and feature flags kept shipping. GitFlow felt like a museum exhibit by year three. #Git #EngineeringPractice #Craft
August 20, 2026 at 4:55 AM
Trunk-based development won the branching war by default. Long-lived feature branches kept aging into merge horror stories, while small daily merges, short-lived branches and feature flags kept shipping. GitFlow felt like a museum exhibit by year three. #Git #EngineeringPractice #Craft
Git branches should live only a day or two for optimal merging and review quality. GitHub Flow is the default choice for most teams, while trunk based development is where high performers end up. GitFlow suits scheduled releases. Feature flags enable short-lived branches for large features. 🌳⏳🚀
Your Branching Debate Is Really About One Number
How long code sits unmerged decides your merge pain, your review quality, and your deploy frequency. Everything else is a consequence of it.
kodekloud.com
August 19, 2026 at 10:40 AM
Git branches should live only a day or two for optimal merging and review quality. GitHub Flow is the default choice for most teams, while trunk based development is where high performers end up. GitFlow suits scheduled releases. Feature flags enable short-lived branches for large features. 🌳⏳🚀
Переосмысление практик DevOps для обработки ускоряющейся пропускной способности разработки
Gitflow может быть отличным подходом к разработке, но он не справляется с объемом pull request'ов. "Непрерывное слияние" быстро рушится, когда у каждого разработчика есть мигр…
Telegram ИИ Дайджест
#ai #news
Gitflow может быть отличным подходом к разработке, но он не справляется с объемом pull request'ов. "Непрерывное слияние" быстро рушится, когда у каждого разработчика есть мигр…
Telegram ИИ Дайджест
#ai #news
Re-thinking DevOps Practices to Handle Accelerating Dev Throughput
hackernoon.com
March 13, 2026 at 10:19 AM
Переосмысление практик DevOps для обработки ускоряющейся пропускной способности разработки
Gitflow может быть отличным подходом к разработке, но он не справляется с объемом pull request'ов. "Непрерывное слияние" быстро рушится, когда у каждого разработчика есть мигр…
Telegram ИИ Дайджест
#ai #news
Gitflow может быть отличным подходом к разработке, но он не справляется с объемом pull request'ов. "Непрерывное слияние" быстро рушится, когда у каждого разработчика есть мигр…
Telegram ИИ Дайджест
#ai #news
As a visual learner, AI tools like ChatGPT and Napkin.AI are game-changers. I ask things like:
👉 “Describe Gitflow so I can sketch a flowchart.”
It works way better than just saying “Make a diagram.”
Clear prompts = clearer learning. #ALX_SE
👉 “Describe Gitflow so I can sketch a flowchart.”
It works way better than just saying “Make a diagram.”
Clear prompts = clearer learning. #ALX_SE
July 5, 2025 at 6:05 PM
As a visual learner, AI tools like ChatGPT and Napkin.AI are game-changers. I ask things like:
👉 “Describe Gitflow so I can sketch a flowchart.”
It works way better than just saying “Make a diagram.”
Clear prompts = clearer learning. #ALX_SE
👉 “Describe Gitflow so I can sketch a flowchart.”
It works way better than just saying “Make a diagram.”
Clear prompts = clearer learning. #ALX_SE
Any positive reference to gitflow is roughly translated as "I dont know what I am talking about, ignore me."
I'd hate to disrespect someone by not acting on that translation. This is being socially responsible.
I'd hate to disrespect someone by not acting on that translation. This is being socially responsible.
June 25, 2026 at 3:12 PM
Any positive reference to gitflow is roughly translated as "I dont know what I am talking about, ignore me."
I'd hate to disrespect someone by not acting on that translation. This is being socially responsible.
I'd hate to disrespect someone by not acting on that translation. This is being socially responsible.
Gitflow Workflow! #BigData #Analytics #AI #MachineLearning #DataScience #IoT #IIoT #Python #RStats #TensorFlow #JavaScript #ReactJS #CloudComputing #Serverless #DataScientist #Linux #Programming #Coding #100DaysofCode
geni.us/Gitflow-Work...
geni.us/Gitflow-Work...
August 5, 2026 at 9:26 PM
智将の人格に関して、初めて81話を見た時に感じたのは接ぎ木か？という印象
なので図はgitflowぽくなってる 上から下へが人格の変化で、左から右へが時間経過を表している
なので図はgitflowぽくなってる 上から下へが人格の変化で、左から右へが時間経過を表している
July 28, 2024 at 10:53 AM
智将の人格に関して、初めて81話を見た時に感じたのは接ぎ木か？という印象
なので図はgitflowぽくなってる 上から下へが人格の変化で、左から右へが時間経過を表している
なので図はgitflowぽくなってる 上から下へが人格の変化で、左から右へが時間経過を表している
While it's amusing, I'm not sure it's real. The link the guy provided doesn't include the AI-ified version of the original Gitflow diagram.
Maybe someone got wise and fixed it, or it never really was.
Maybe someone got wise and fixed it, or it never really was.
February 17, 2026 at 8:05 PM
While it's amusing, I'm not sure it's real. The link the guy provided doesn't include the AI-ified version of the original Gitflow diagram.
Maybe someone got wise and fixed it, or it never really was.
Maybe someone got wise and fixed it, or it never really was.
... wait hold up.
Do you mean both of them get yeeted by some unspecified means, or that the gitflow guy gets yeeted by using the webp fucker as some kind of human trebuchet?
Do you mean both of them get yeeted by some unspecified means, or that the gitflow guy gets yeeted by using the webp fucker as some kind of human trebuchet?
April 12, 2026 at 8:08 PM
... wait hold up.
Do you mean both of them get yeeted by some unspecified means, or that the gitflow guy gets yeeted by using the webp fucker as some kind of human trebuchet?
Do you mean both of them get yeeted by some unspecified means, or that the gitflow guy gets yeeted by using the webp fucker as some kind of human trebuchet?
- There is a new example project that demonstrates the scale/rotate functions on the Mega CD hardware.
- The repo has moved to gitflow in an attempt to have a proper release architecture.
- The repo has moved to gitflow in an attempt to have a proper release architecture.
March 14, 2026 at 6:31 AM
- There is a new example project that demonstrates the scale/rotate functions on the Mega CD hardware.
- The repo has moved to gitflow in an attempt to have a proper release architecture.
- The repo has moved to gitflow in an attempt to have a proper release architecture.
There’s only one way to do software on git.
Never use gitflow, never separate dev and prod branch, never use git rebase and never rewrite the git history.
The only way to use git is a single main branch and short-lived pull request branches squashed merged once tests passed. That’s it.
Never use gitflow, never separate dev and prod branch, never use git rebase and never rewrite the git history.
The only way to use git is a single main branch and short-lived pull request branches squashed merged once tests passed. That’s it.
October 20, 2025 at 5:33 AM
There’s only one way to do software on git.
Never use gitflow, never separate dev and prod branch, never use git rebase and never rewrite the git history.
The only way to use git is a single main branch and short-lived pull request branches squashed merged once tests passed. That’s it.
Never use gitflow, never separate dev and prod branch, never use git rebase and never rewrite the git history.
The only way to use git is a single main branch and short-lived pull request branches squashed merged once tests passed. That’s it.
Good morning. Please know that if you don’t use a documented #versioning model like #gitflow or others, we are enemies, and we draw pistols at dawn.
February 15, 2023 at 2:46 PM
Good morning. Please know that if you don’t use a documented #versioning model like #gitflow or others, we are enemies, and we draw pistols at dawn.
If you have seen memes of Tim continvoucly morging and didn't understand what has happened, the answer is of course: AI Slop. Thanks, Microsoft
https://nvie.com/posts/15-years-later/
#microsoft #ai #gitflow
https://nvie.com/posts/15-years-later/
#microsoft #ai #gitflow
15+ years later, Microsoft morged my diagram
How Microsoft continvoucly morged my Git branching diagram.
nvie.com
February 20, 2026 at 1:03 PM
If you have seen memes of Tim continvoucly morging and didn't understand what has happened, the answer is of course: AI Slop. Thanks, Microsoft
https://nvie.com/posts/15-years-later/
#microsoft #ai #gitflow
https://nvie.com/posts/15-years-later/
#microsoft #ai #gitflow