branching-and-merging

Why am I merging “remote-tracking branch 'origin/develop' into develop”?

强颜欢笑 提交于 2019-11-28 14:55:21
I'm the only one in my organization who's making commits with the following message: Merge remote-tracking branch 'origin/develop' into develop Not sure what I'm doing to cause them, but I'd like to stop. What command am I issuing to create this commit, and what is the proper command I ought to be using to not produce it? Richard Hansen git pull is probably creating the commit. If you make a local commit and then run git pull after someone else pushes a commit up to the repository, Git downloads the other developer's commit and then merges it into your local branch. How to avoid these merge

git tells me that I Merge conflict, but also tells me that no files need merging

落爺英雄遲暮 提交于 2019-11-27 22:17:34
问题 I committed some changes in the branch new . I checkout out to master . When I tried to merge: $ git merge new Auto-merging js/site.js CONFLICT (content): Merge conflict in js/site.js Automatic merge failed; fix conflicts and then commit the result. So I installed kdiff3 and configured my config files and when I tried to use mergetools I got: $ git mergetool kdiff3 No files need merging I ran a diff and it outputted this: diff --cc js/site.js index 8c17d62,7955b13..0000000 --- a/js/site.js ++

Git merge diff3 style need explanation

戏子无情 提交于 2019-11-27 20:04:47
问题 I've merged 2 branches and conflicts appeared, I would need some hints where it starts where it ends, etc. I've replaced the code with some faked data to make it easier to read and talk about. <<<<<<< HEAD aaaaaa ||||||| merged common ancestors <<<<<<< Temporary merge branch 1 bbbbbb ======= cccccc >>>>>>> mybranch dddddd <<<<<<< HEAD eeeeee ||||||| merged common ancestors ffffff ||||||| merged common ancestors gggggg ======= >>>>>>> Temporary merge branch 2 ======= hhhhhh >>>>>>> mybranch

Git octopus merge order of multiple branches

久未见 提交于 2019-11-27 17:59:21
I had an interesting thing happen using git, wondering if anyone could explain it to me so I can understand better. When doing a merge of multiple branches (A,B), git merge A B fails as non-fast-forward, while git merge B A worked well. Why would that be? huitseeker Let's assume that A is a strict, direct child of the current branch. Then assume that B is a strict, direct child of A . The octopus merge, which processes heads given as arguments from left to right , incrementally with respect to the tree , but independently with respect to the index succeeds without conflict if it tries to apply

Proper git workflow scheme with multiple developers working on same task

怎甘沉沦 提交于 2019-11-27 17:20:29
I'm a team leader in our web development company, and I'd like to implement Git workflow in our team. Reading documentation and articles I've found the following structure good for us: We have a repository in a Bitbucket. Master branch is considered to contain stable code only. Every dev must create his own branch and implement features/bugfixes in his own branch. Once he decides, that his code is ready, he creates a nice branch history (using rebase, amend, cherry-pick etc.) and pushes it to Bitbucket, where creates a pull request to master branch. QA verifies functionality and approves (or

Tortoisesvn Subversion 1.8 - merge - no more reintegrate a branch option

早过忘川 提交于 2019-11-27 17:12:15
In tortoiseSvn 1.8 there is no "reintegrate" a branch option. What is the right way to reintegrate a branch in Tortoise Svn 1.8? In choose merge and then next option: Then I get next window: Or am I doing something else wrong? Just merge branch to any TARGET Edit OK, extended answer: "Merge for Dummies" in pictures Preface OK, I will not mask or hide used proving ground. Used in this sample resources: Repository "Hello, World" http://mayorat.ursinecorner.ru:8088/svn/Hello/ Branch http://mayorat.ursinecorner.ru:8088/svn/Hello/branches/branche-francaise Trunk of repo http://mayorat.ursinecorner

How to resolve git's “not something we can merge” error

泄露秘密 提交于 2019-11-27 16:58:28
I just encountered a problem when merging a branch into master in git. First, I got the branch name by running git ls-remote . Let's call that branch "branch-name". I then ran git merge branch-name command and got the following result: fatal: branch-name - not something we can merge How do I resolve this error? Brian As shown in How does "not something we can merge" arise? , this error can arise from a typo in the branch name because you are trying to pull a branch that doesn't exist. If that is not the problem (as in my case), it is likely that you don't have a local copy of the branch that

How do I get the SCM URL inside a Jenkins Pipeline or Multibranch Pipeline?

人盡茶涼 提交于 2019-11-27 16:11:51
问题 I am trying to get a prebuild merge to work inside a multibranch pipeline and I would like to avoid having to hardcode the git url in my pipeline script. It seems like scm step must store the url somehow, but I cannot figure out how to access it. 回答1: You are correct, the scm object does have the information you need. When using git as the source control in a Pipeline project (or Multibranch Pipeline project), the scm global variable will be an instance of GitSCM. That means that `scm

How to find all unmerged commits in master grouped by the branches they were created in?

你离开我真会死。 提交于 2019-11-27 15:54:53
问题 I have to create some code review from unmerged branches. In finding solutions, let's not go to local-branch context problem as this will run on a server; there will be just the origin remote, I will always run a git fetch origin command before other commands, and when we talk about branches, we will refer to origin/branch-name . If the setup were simple and each branch that originated from master continued on its own way, we could just run: git rev-list origin/branch-name --not origin/master

How can I recover from “fatal: Out of memory? mmap failed: Cannot allocate memory” in Git?

混江龙づ霸主 提交于 2019-11-27 14:51:45
问题 Let me start with some context: I had to upgrade a crucial Magento webshop to a new version. To be sure all existing code would still work after the upgrade and make some post-upgrade changes I made a Git repository from the entire Magento installation (excluding obvious content like the 4.5GB of images, ./var directory etc.), pushed it to an origin and cloned it on a dev server. Made a new branch, performed the upgrades, made code changes, committed it all to the dev branch and pushed it