Those who don’t need too much permission management like to use git, but those who have permission management will not use it. The company used the commercial version of Perforce before. The reason is very simple. Once tens of millions of submitted code changes crash, the loss to the company will be huge. Even if there is a backup, the company is not willing to be the first to try it
Interesting, someone actually stepped on me I wonder if the person who stepped on me has ever worked in a big company. I know a few large companies that don’t use git. It’s very simple. Who has the time to worry about the company’s business? Can passwords be managed distributedly using git? For example, Google's VCS is even a set of tools developed by itself. In a team with more than a few thousand people, once the company's business secrets are involved, the company will not release the core competitiveness code. I don’t intend to start a debate, but don’t regard git as a god. It is just a version management tool. In addition to git, there are many VCS companies, such as hg and p4. Whether a company uses git depends on the company’s technical atmosphere and strategy. related.
I would like to add that small-scale Internet companies like to use git. The reason is simple. Operations of service-oriented Internet companies are more important than technology. Not many traditional service companies completely convert their code to git
Our company is engaged in .net development, using all Microsoft technologies. So our company uses TFS. And TFS also supports git. TFS can perform complete life cycle management.
I feel that git has no advantages in enterprise development. Its functions are basically the same as svn. In remote collaborative development, it feels fine and there is no need to change.
This depends on the size of the product, the size of the development team, and the speed of iteration. . . If your code needs to be developed in several branches at the same time, has a Code Review process, and is released in many environments, then using git will be very convenient. Using SVN in this scenario is basically finished
If you don’t use git now, you may just be considered low. In a few years, if you don’t know how to use it, you will be considered out. As far as I know, most new teams and new projects are currently choosing to use git. , those who use svn are mostly old projects, and they are all switching to git. I have only used version control, so git is enough. If you want to do more things (such as permissions, review, etc.), gitlab is recommended
https://github.com/xirong/my-git/blob/master/git-workflow-tutorial.md
This article explains the Git workflow in detail
Those who don’t need too much permission management like to use git, but those who have permission management will not use it.
The company used the commercial version of Perforce before. The reason is very simple. Once tens of millions of submitted code changes crash, the loss to the company will be huge. Even if there is a backup, the company is not willing to be the first to try it
Interesting, someone actually stepped on me
I wonder if the person who stepped on me has ever worked in a big company. I know a few large companies that don’t use git. It’s very simple. Who has the time to worry about the company’s business? Can passwords be managed distributedly using git? For example, Google's VCS is even a set of tools developed by itself. In a team with more than a few thousand people, once the company's business secrets are involved, the company will not release the core competitiveness code.
I don’t intend to start a debate, but don’t regard git as a god. It is just a version management tool. In addition to git, there are many VCS companies, such as hg and p4. Whether a company uses git depends on the company’s technical atmosphere and strategy. related.
I would like to add that small-scale Internet companies like to use git. The reason is simple. Operations of service-oriented Internet companies are more important than technology. Not many traditional service companies completely convert their code to git
Traditional software industry development is not used much.
Most of the emerging Internet companies are using it.
Our company is engaged in .net development, using all Microsoft technologies. So our company uses TFS.
And TFS also supports git. TFS can perform complete life cycle management.
Currently, svn is more popular
I feel that git has no advantages in enterprise development. Its functions are basically the same as svn.
In remote collaborative development, it feels fine and there is no need to change.
Not sure, at least our company and Ele.me use git, Ele.me uses GitHub, and my company uses Git Stash
This depends on the size of the product, the size of the development team, and the speed of iteration. . .
If your code needs to be developed in several branches at the same time, has a Code Review process, and is released in many environments, then using git will be very convenient.
Using SVN in this scenario is basically finished
If you don’t use git now, you may just be considered low. In a few years, if you don’t know how to use it, you will be considered out.
As far as I know, most new teams and new projects are currently choosing to use git. , those who use svn are mostly old projects, and they are all switching to git.
I have only used version control, so git is enough. If you want to do more things (such as permissions, review, etc.), gitlab is recommended