branch - Storing separate named branches in mercurial without having to merge them -
This is also for the first time as a DVCs and also as a sole developer, for the first time when I actually used the branches , So maybe I'm missing something here.
I have a remote repository, from which I was able to pull the file and start working. The change was pushed into the remote repository and of course this simple scenario works fine.
Now that there are some stable features in my web application, I would like to start deploying it and therefore I tried to clone the remote repository for new branches / static directories for the default branch of their branch. And used:
hg branch static
to create a new named branch. I have created a group of deployment scripts which are only required by the stable branch and I have committed them as necessary. Again it works fine.
Now when I went back to my initial working directory to work on some new features, I found out that Mercurial only emphasizes the same head in a remote repository. In other words, I have to merge two branches (default and constant), to add to the main collection the unnecessary deployment script must be added to my default branch. It can be worse, if I had to make a change in a file in my stationary branch to deploy.
How do I keep my enrolled branches in Mercury? Do I have to create two separate remote repositories to do this? In what case the named branches lose their value, am I missing something here?
To force enforcement, use hg push -f
to create a new one Remote head build.
The reason Push
will not do this by default that it is trying to remind you that when you forget to drag and merge it What do you not want to do:
- You and me can check the amendment of 100 nominated branches "X".
- You are committed locally and push
- I am locally committed and push.
Now the branch looks like X in a remote repo in this way:
- - (100) - (101) \ \ ----- ---- (102)
If they are checking the branch, then what new head should the new developer catch? Who knows.
Comments
Post a Comment