Git never (auto) merge composer.json -


I have my compositor GI In this way, I can develop a composer. Jason, who uses development-development package, while one of the master uses only the Dev-Master package.

According to the suggestion, I can use two composer.json files, but I am afraid that I will have my composer for the master. Jason will forget to add a bundle. Especially when automating tasks, it can end in a disaster.

In fact, I would like GIT either:

  • There is always a dispute while merging composers, so I
  • based on the number of lines only Merge on .. So if a bundle is added / removed, then the number of lines changes, then merge it, struggle, whatever, if the content of the change in a row changes, then ignoring it

    While I I believe that the special scenario you have indicated indicates that you have in-depth problems with your development process, that you set the merge attribute on file in question By making GIT easy to ask, one of the two values, from the "Merge in three ways" section of the GIT Help Attributes, they are:

    Merge unset

    version to version Let's take as temporary merge results from the branch, and declared that the conflict in the merge. This is suitable for binary files, which do not have a well defined merge word rating.

    To install it, please:

      echo "composer.json - merge" & gt; & Gt; .gitattributes   

    merge = binary

    Keep a version from your branch in the work tree, but leave it in the path to solve the user Disputed status for

    To install it, please:

      echo "composer.json merge = binary" & gt; & Gt; .gitattributes   

    both behave the same

    These descriptions do not really explain how behaviors differ, and in fact, after testing, these Both of these outputs produce $ Git merge: Warning: Binary files can not be merged: composer.json (Head vs. Development) Auto-Merge Composer Jason Conflix (Contents): Composer. Merge merge merge into Jason Automatic Merge Failure; Correct the conflicts and then give results. $ Git's status branch attr-test-2 has unarmed the path (fix the dispute and run "git commit") the paths were unplanned: ("git add and lieu file" to mark the resolution Gt; ... ") both modified: no changes were added to commit composer.json (" git add "and / or" git commit -a ")

    Since you want that the semantics are not necessarily to declare that this file is binary, but only to git it Wchalit for not disclosing to merge, -mirge It seems a little bit better.

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -