-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master and Beta VM #1
Comments
I'm not sure about that. |
You can easly sync 2 branches by using Let try and see if there is big issue!? |
I don't mean the synchronization of w4m-docker or w4m-vm branches. I mean the synchronization between the two branches inside w4m-config. I can't see how it can be easy. The lists of tools can't be merged "as is", there is no reason we will just make a copy of beta tool list onto release tool list. |
And indeed, you are right that the contain of the tool_list will be edit by hand. |
Ok, I will create a branch We should also rename those file by removing |
Yes, please, undo. |
Undo: done |
@pierrickrogermele
What do you think about that? ( hopefully, it's not to late to reverse 😄 )
Within this repository w4m-config maintain 2 branches:
with to list of tools. master will for instance target the main toolshed and beta the testtoolshed.
In parallel, within w4m-docker and w4m-vm we have the same system with 2 branches:
which will target their cousin w4m-config/master and w4m-config/beta:
.gitmodules/.gitmodules#L16
I kept master but maybe we should rename this branch lastest to fit with the docker nomenclature?
The text was updated successfully, but these errors were encountered: