Hi everyone

 I'm totally stuck with a following problem:

- we have a repo, which contains several projects as folders - like "api", "adminUI", "android", "web" - etc. Some parts are backend, some frontend. Lets name these parts "details", as they constitute details of the project in general. - we would like to deploy via git, so as to minimize effort on deployment (and automate it later).
- but every project is deployed separately.

From all I've read so far, I came to conclusion that "merge -s subtree" seems to be done with this thing in mind, although scenarios, described in articles like this one (https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html) usually take only one part of it: merge from "detail" to "common", and not vice versa.

So, what am I trying to: to implement a stable workflow, that would allow me to easily merge changes from "develop" in "common" repo to a "subtree-branch" and push to a corresponding "detail" remote.

What I am doing:

1) say, we have a folder "adminUI" in the root of "common" repo, branch "test" (it's a snapshot branch for test environment - all deploys should start here)
2) git remote add adminui-origin <path>
3) git fetch adminui-origin
4)  git checkout -B test-adminui adminui-origin/test
(above steps are taken from http://git-scm.com/book/en/v1/Git-Tools-Subtree-Merging)
5) git checkout test
6) git merge -s ours --no-commit test-adminui
(this one is from https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)
7) git read-tree --prefix=adminUI/ -u test-adminui
Here I always get error like:
error: Entry 'adminUI/.gitignore' overlaps with 'adminUI/.gitignore'. Cannot bind.

8) so, I have to rename folder "adminUI" to, like, "adminUI2", then "git commit -a", then step 7 again 9) ok, so now I have a whole content of "adminui-origin" in folder "/adminUI" in branch "test" of my "common" repo. 10) then I merge changes from "develop", which I want to deploy: git merge develop
11) then I want to merge those changes "down the line" into "detail" repo:
git checkout test-adminui
git merge -s subtree test
12) for the first time, everything seems fine - only relevant changes (i.e., changes in adminUI folder) are merged, and they go straight into their right places (i.e., with respect to folder structure difference between "common" and "detail")
13) git push adminui-origin test-adminui:test  - this works good
14) let's say something else was updated in develop:
git checkout test
git merge develop
git checkout test-adminui
15) AND HERE BEGINS THE HELL:
git merge -s subtree test => leads to ALL of my working directory being copied to a 3rd level folder somewhere in the adminUI depths !!!

This drives me TOTALLY insane, and I very much need help !!

I use msysgit 1.9.4 on Windows 8.1

I suspect that it might have to do with the repository structure, maybe some errors, etc..

But I believe that it might be due to my total misunderstanding of something

Anyway, I totally appreciate your help !

Thanks a lot

Kirill, frustrated unexperienced git user...

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to