Can you explain why you blocked the remote branch in Git?

I made an introductory presentation on GIT when an audience member asked me how to block a remote branch, preventing a push from someone else.

I understand why the person who uses TFS knows about this, but are there any reasons why you would need to block the remote repository in GIT? If so, which ones?

+4
source share
3 answers

Locking a branch in TFS makes it read-only (see " Creating a TFS branch read-only ")

Git : git, ( ), .

, :

, ( ), .

+4

git ( : , ), , - ? - : .

, : SCM , , , (/main/trunk/ .. ).

, , , , v2.1, ​​ QA , , v2.1, , v2.1. master, v2.2, v2.5, Experimental-feature-branch ..

v2.1 .

, git , ( SCM/SQA , , ), , , "" , ?

svn . A git - , , : " !", , , - .

, , git!:)

0

git "" . , :

git tag v0.1.37
git push --tags

, . , , , . , -, . git , , ( --force), ( , ).

Alternatively or additionally, you can use gitosis , gitloite, and other additional tools to provide better security.

-1
source

All Articles