gitflow README

The project's README from github.com/nvie/gitflow. As one markdown file: README.md.

[!IMPORTANT]

⚠️ git-flow has moved to git-flow-next!

This repository is no longer maintained. The wonderful team at Tower has created git-flow-next — a modern, fully customizable evolution of git-flow, built on a generic branch dependency model. It’s fully backward compatible with git-flow, open source, and actively maintained.

Get started with git-flow-next:

Why git-flow-next?

git-flow-next builds upon the foundation laid by the original git-flow, offering:

  • Full customization of branch names and workflow
  • Modern implementation with active maintenance
  • Backward compatibility with existing git-flow workflows
  • Upcoming features like stacked branches and topic branch syncing

Thank you ❤️

To everyone who has used, contributed to, and supported git-flow over the past 15+ years — thank you! Your feedback, contributions, and adoption made git-flow one of the most widely-used Git workflow tools. Special thanks to Peter van der Does for maintaining git-flow-avh, and to the folks at Tower for carrying the torch forward with git-flow-next.


(Below, you’ll find the original documentation for historical reference.)


git-flow

A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model.

Getting started

For the best introduction to get started with git flow, please read Jeff Kreeftmeijer's blog post:

http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/

Or have a look at one of these screen casts:

Installing git-flow

See the Wiki for up-to-date Installation Instructions.

Integration with your shell

For those who use the Bash or ZSH shell, please check out the excellent work on the git-flow-completion project by bobthecow. It offers tab-completion for all git-flow subcommands and branch names.

FAQ

See the FAQ section of the project Wiki.

License terms

git-flow is published under the liberal terms of the BSD License, see the LICENSE file. Although the BSD License does not require you to share any modifications you make to the source code, you are very much encouraged and invited to contribute back your modifications to the community, preferably in a Github fork, of course.

Initialization

To initialize a new repo with the basic branch structure, use:

	git flow init [-d]

This will then interactively prompt you with some questions on which branches you would like to use as development and production branches, and how you would like your prefixes be named. You may simply press Return on any of those questions to accept the (sane) default suggestions.

The -d flag will accept all defaults.

Creating feature/release/hotfix/support branches

gitflow (nvie/gitflow)

Searching Database…

26.8K ·GitHub
archived
这是什么?这是一组 Git 扩展,实现了 Vincent Driessen 提出的分支模型,在普通 git 之上增加了用于管理功能、发布、热修复和支持分支的高级命令。
这是独立的应用,还是通过 git 本身运行的?它不是独立的应用,而是一个 shell 脚本,会添加一个 'git flow' 子命令,所以你可以像使用其他 git 命令一样,在现有的仓库中直接使用它。
我该如何在一个仓库上开始使用 git-flow?在 git 仓库中运行 'git flow init'(或运行 'git flow init -d' 以接受所有默认设置);它会以交互方式询问开发分支和生产分支分别使用哪些分支,以及前缀如何命名。
除了 git 本身,我还需要别的东西吗?只需要 git 和 shell;Bash 和 ZSH 用户可以选择额外安装 bobthecow 开发的独立项目 'git-flow-completion',以便对子命令和分支名称使用 Tab 补全。
这个项目还在维护吗?已不再维护,该仓库已归档。作者建议用户改用 'git-flow-next',这是 Tower 团队开发的现代化、持续维护且向后兼容的后继项目。
git-flow 管理哪些类型的分支?它管理功能、发布、热修复和支持分支,每种分支都有各自的 start、finish、publish、pull 命令,并与 develop 或 master 等特定的基础分支绑定。
为什么 git-flow 被弃用并转而推荐 git-flow-next?git-flow-next 由 Tower 开发,提供分支名称和工作流的完全自定义,是现代化且持续维护的实现,兼容现有的 git-flow 仓库,并计划推出堆叠分支等新功能。
git-flow 命令可以使用 shell 的 Tab 补全吗?可以,Bash 和 ZSH 用户可以安装 bobthecow 开发的独立项目 git-flow-completion,以便对子命令和分支名称使用 Tab 补全。
What are similar projects?git-extras, autojump, just, cz-cli, lazygit, epiq, prezto, oh-my-posh
Creator
nvie
Size
0.5 MB
Stars
26.8K
Updated
CommitOct 14
Age
16y
Commits · 90 Days