|Best practices new branches, switching branches and projects that disappear? [message #783955]
||Thu, 26 January 2012 15:34
| Cameron Missing name
Registered: November 2011
So picture a git environment where you have:|
main branch->qa branch->dev branch->features
When a feature branch is merged down to the dev branch, continuous integration picks it up and deploys it to development.
So now I have a new feature I want to create:
1. Create new branch feature hello world
2. Branch switches automatically to the new branch "hello world"
3. I create a new project and create hello world
4. Commit changes to the branch
5. Switch back to the development branch, I am ready to merge this down.
---- Problem at this point -----
Since my project does not exist in the development branch it has been removed from eclipse as a project. What a bummer.
6. Merge the branch in.
7. Import the project and redeploy it to my local server.
What I am looking for is the best practice for my problem area.
I could create the empty project in the development branch, then create my feature branch. That way the project would still exist when moving between branches.
Powered by FUDForum
. Page generated in 0.01500 seconds