merge-conflict-resolution

GitLab merge behavior - keep file from branch

僤鯓⒐⒋嵵緔 提交于 2021-02-08 07:58:29
问题 Is it possible to default to one branche's version of a file when doing merge requests in GitLab Web Interface? I'm trying to set up the GitLab Web Interface, so that you can use the graphical interface to do merge requests. In these merge requests, certain files on the target branch must not be subject to any changes. Most often, I'm working on web projects with a config.php, and here we can see how it's possible to not overwrite the config in branch 'prod' with anything (ie from 'dev')

Exclude certain file patterns from rename detection in git?

独自空忆成欢 提交于 2021-02-08 06:35:59
问题 Question Is it possible to exclude certain file patters from rename detection when doing merges with git? Background With our system, Salesforce.com, some metadata files are exactly identical, except for name. Because of this (I believe) merges can get a bunch of conflicts, e.g. if a meta file was deleted in one branch, and a different meta file with an identical body is deleted in another, it sees things as a rename and conflict with one added on deleted. I know I can tweak the sensitivity

Intentionally create Merge Conflict

谁说我不能喝 提交于 2021-02-07 14:40:35
问题 I have pulled the files from GitHub already. Now I need to create a merge-conflict. How do I intentionally create a merge conflict on GitHub? 回答1: Edit the same line in two branches, and try to merge Merge conflicts in git happen, when two branches were changed on the same line or in the same content of a file before a merge. If you just extend a file or append something, git usually just figures it out by itself. Use this code: #!/bin/bash mkdir git-repo cd git-repo git init touch my_code.sh

Intentionally create Merge Conflict

六月ゝ 毕业季﹏ 提交于 2021-02-07 14:39:30
问题 I have pulled the files from GitHub already. Now I need to create a merge-conflict. How do I intentionally create a merge conflict on GitHub? 回答1: Edit the same line in two branches, and try to merge Merge conflicts in git happen, when two branches were changed on the same line or in the same content of a file before a merge. If you just extend a file or append something, git usually just figures it out by itself. Use this code: #!/bin/bash mkdir git-repo cd git-repo git init touch my_code.sh

CoreData merge conflict shows managed object version change not data

时光怂恿深爱的人放手 提交于 2020-12-26 07:19:17
问题 I am have an entity in core data and I try to update it from two different context. I am storing managedObjectID of my managed object which I need to update as it is thread safe. Before updating my object I refresh the object to avoid merge conflict. Here is my code: context1.performBlock { let myObject = context1.objectWithID(managedObjectId) context1.refreshObject(myObject, mergeChanges: true) myObject.property1 = newValue } Notice that I haven't saved the context here, as I want to commit