Native git does not have permission settings. Now those who have permission requirements use github or gitlab and other git-based online code management platforms (which also come with more powerful functions). For those who have private deployment requirements, only gitlab currently provides a community. version system, there are also Chinese docker images It is not recommended to use svn, the risk of losing code version records is still much higher than git @ZXCDFGTYU
I once used Gitolite to assign permissions to git projects, and it worked well
If a new person comes to the company and clones the entire code, will there be any problem?
If everything in the entire company is in one warehouse and others are not allowed to clone it, how can others develop it? If there are several, corresponding permissions will be given.
Set permissions. Git is generally divided into public and private. Generally, private ones need to be added to a group before they can be cloned. Can be set within the project.
If you want to set permissions, you still need to use svn. After all, the original intention of git design is open sharing. It is quite troublesome to set permissions in git. It is not as good as svn. Just set it in the configuration file and it also has hooks
Gitlab can be used, but when you give permission, it will still clone all the code. . . I would like to say that I have the front-end codes of several internship companies in my computer. As long as I have a learning attitude, check it out and don’t do any transactions, I think it’s fine
Native git does not have permission settings. Now those who have permission requirements use github or gitlab and other git-based online code management platforms (which also come with more powerful functions). For those who have private deployment requirements, only gitlab currently provides a community. version system, there are also Chinese docker images
It is not recommended to use svn, the risk of losing code version records is still much higher than git @ZXCDFGTYU
I once used Gitolite to assign permissions to git projects, and it worked well
If everything in the entire company is in one warehouse and others are not allowed to clone it, how can others develop it? If there are several, corresponding permissions will be given.
ps: To quote Liao Dada: Code is worthless now
Set permissions. Git is generally divided into public and private. Generally, private ones need to be added to a group before they can be cloned. Can be set within the project.
If you want to set permissions, you still need to use svn. After all, the original intention of git design is open sharing. It is quite troublesome to set permissions in git. It is not as good as svn. Just set it in the configuration file and it also has hooks
git does not. . . Git has full permissions
Gitlab can be used, but when you give permission, it will still clone all the code. . .
I would like to say that I have the front-end codes of several internship companies in my computer. As long as I have a learning attitude, check it out and don’t do any transactions, I think it’s fine