After the git fork project, the merge request will retain the source library relationship to avoid mismerging operations.

After the git fork project, the merge request will retain the source library relationship to avoid accidental merge operations.

1. For example, when you fork another project on gitlab, you are pulling a branch from the trunk when developing new requirements, and you need to merge into the trunk. Click the Merge Request button below.

2. At this time, you will find that the default merge target branch is the trunk branch of the old library. If you do n’t look closely, you may continue to submit it to the wrong trunk. The current premise is to have permissions.

 

 3. Therefore, you need to disconnect the relationship with the source project to avoid this problem. You need to Remove the relationship in the project's setting configuration, as follows.

 

 

 4. At this point, after re-initiating the merge request, there is only one target branch trunk.

 

Guess you like

Origin www.cnblogs.com/xuzhujack/p/12744255.html